From: W C W on
Phil, thanks so much, I ran into the same issue when migrating from sbs 2003
to sbs 2008, I have used hosts file to resolve dns issue before, but never
during migration especially when error screen didn't indicate any other
options, thanks for saving me from needless frustration.

W C

"Phil Rodgers (Open GI)" wrote:

>
>
> "Don" wrote:
>
> > So I checked the ports on the switch and yes, they were different in their
> > config for vlans, but I changed them to be the same and still nothing.
> > Operaing only on vlan1 data.
> >
> > Still lost.
>
>
> >
> > "Don" wrote:
> >
> > > I'm having the same issue. I read through the above suggestions and fixed
> > > all that were different. The only other thing I'm doing different is the IP
> > > addressing.
> > >
> > > Source = 172.16.17.2
> > > dest = 172.16.17.6
> > > gate = 172.16.255.254 (managed switch)
> > > subnet 255.255.0.0
> > >
> > > Problem is, I can't take the time to change the IP addressing to the
> > > suggested 192.168.etc.. because my office never closes.
> > >
> > > I did however find another post that said my addressing would work fine and
> > > I can ping the source by address and fqdn from the destination server.
> > >
> > > From the dest server I opened a CMD prompt and ipconfig looks good (same
> > > subnet, correct gateway, etc...)
> > >
> > > Would vlans on the switch have an impact on this?
> > >
> > >
>
>
> Dan and all,
>
> I had the same issue and was completely stuck for hours, even after trying
> all the suggestions above in these threads.
>
> I could resolve my swingsbs (source) by netbios name from a workstation and
> ping either way, leaving me evenmore confused.
>
> Eventually, by pressing ctrl + alt + del on the SBS2008 I managed to launch
> task manager, clicked file > run, typed explorer.exe and added a host entry
> for my swingsbs (source) by navigating to
> c:\windows\system32\drivers\etc\hosts, once I had done this the setup
> continued.
>
> In fact you can access pretty much anything on the SBS2008 by doing this, so
> greatly helps with troubleshooting.
>
> I hope this saves someone elses frustration!
>
> Phil.