moved server no no connection problem

Hi,
I will try to explain my problem below but basically I would like to know
why some computers can pick up the shared drives on the server and the
others can't even though they all worked fine before the move?

We have moved our offices to 2 new locations with the users in one office
and the server to another office and setup a LAN to LAN VPN using Draytek
routers. This is working fine. I have 6 pc's that log onto the network and
then a script runs that sets up the mapped network drives. When this has run
then the shared files, my docs, email (exchange server) and sage all work
fine. My problem is that 3 of the PC's run this script at login and connect
without any problems. 3 don't run the script (not sure why) and I can't get
them to log onto the mapped network drives and the exchange emails don't
work. I can ping the Server IP and also access the files via the IP address
but not throught he Server name?

First thing I would like to do is make sure that the script runs on all the
computers but I don't know where to find it? I am sure that it used to run
on all 6 PC's (XP Pro).

On the 3 PC's that work I can use 'run' \\servername. On the 3 PC's that
don't work I can't do that, it tells me that there domain isn't available
but if I \\192.168.X.X then it brings the folder up OK.

Any help greatly appreciated.

 

HI Lenny:

Do I understand correctly that the remote office has 6 computers, half of
which can resolve the name of the SBS which is in a remote office, and the
other half cannot?

Try this: start - run - cmd - type "ipconfig /all" without quotes, on one
that works and one that does not, and compare the results carefully. The
three that work are getting proper resolution from whatever DNS server they
are pointed to, the other three are not.

Then, on the three that don't work, ipconfig /release, which should reset
the ip info to all 0's, followed by ipconfig /renew.

Also, verify that both sets are setup to receive IP's from DHCP, and that
the three that don't work are not static left over from some prior config.

Then, after all the above: ipconfig /flushdns then ipconfig /registerdns.

And let us know the results.

The logon script is in C:\windows\sysvol, iirc, but unless the permissions
are different, all users should run this on logon. I sometimes put a pause
in the script to verify it has actually run. If you can't find it, on the
SBS search for logon.bat. You should find two, but they live in replicating
folders so that changes to one copy will appear in the other before you can
open it.

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:



"lenny109" <lenny@thetakeout.com> wrote in message
news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> I will try to explain my problem below but basically I would like to know
> why some computers can pick up the shared drives on the server and the
> others can't even though they all worked fine before the move?
>
> We have moved our offices to 2 new locations with the users in one office
> and the server to another office and setup a LAN to LAN VPN using Draytek
> routers. This is working fine. I have 6 pc's that log onto the network
> and then a script runs that sets up the mapped network drives. When this
> has run then the shared files, my docs, email (exchange server) and sage
> all work fine. My problem is that 3 of the PC's run this script at login
> and connect without any problems. 3 don't run the script (not sure why)
> and I can't get them to log onto the mapped network drives and the
> exchange emails don't work. I can ping the Server IP and also access the
> files via the IP address but not throught he Server name?
>
> First thing I would like to do is make sure that the script runs on all
> the computers but I don't know where to find it? I am sure that it used to
> run on all 6 PC's (XP Pro).
>
> On the 3 PC's that work I can use 'run' \servername. On the 3 PC's that
> don't work I can't do that, it tells me that there domain isn't available
> but if I \192.168.X.X then it brings the folder up OK.
>
> Any help greatly appreciated.
> <!--colorc--><!--/colorc-->

 

Hi Larry,
Thanks for the reply. Yes you are correct in the first paragraph. You have
managed to say in one paragraph exactly what I was trying to say in 4 long
ones!

I have checked all the IP's to make sure they are set to Auto and I also
tried setting them to static then back to Auto as they are now. They can
access the internet OK. IPconfig is the same (except for the IP address
obviously) on both a working PC and one that isn't.

I haven't flushed the DNS yet but will as soon as I can get back in the
office.

"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> HI Lenny:
>
> Do I understand correctly that the remote office has 6 computers, half of
> which can resolve the name of the SBS which is in a remote office, and the
> other half cannot?
>
> Try this: start - run - cmd - type "ipconfig /all" without quotes, on one
> that works and one that does not, and compare the results carefully. The
> three that work are getting proper resolution from whatever DNS server
> they are pointed to, the other three are not.
>
> Then, on the three that don't work, ipconfig /release, which should reset
> the ip info to all 0's, followed by ipconfig /renew.
>
> Also, verify that both sets are setup to receive IP's from DHCP, and that
> the three that don't work are not static left over from some prior config.
>
> Then, after all the above: ipconfig /flushdns then ipconfig /registerdns.
>
> And let us know the results.
>
> The logon script is in C:windowssysvol, iirc, but unless the permissions
> are different, all users should run this on logon. I sometimes put a
> pause in the script to verify it has actually run. If you can't find it,
> on the SBS search for logon.bat. You should find two, but they live in
> replicating folders so that changes to one copy will appear in the other
> before you can open it.
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
> Get a Health Check for SBS at:
>
>
>
> "lenny109" <lenny@thetakeout.com> wrote in message
> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi,
>> I will try to explain my problem below but basically I would like to know
>> why some computers can pick up the shared drives on the server and the
>> others can't even though they all worked fine before the move?
>>
>> We have moved our offices to 2 new locations with the users in one office
>> and the server to another office and setup a LAN to LAN VPN using Draytek
>> routers. This is working fine. I have 6 pc's that log onto the network
>> and then a script runs that sets up the mapped network drives. When this
>> has run then the shared files, my docs, email (exchange server) and sage
>> all work fine. My problem is that 3 of the PC's run this script at login
>> and connect without any problems. 3 don't run the script (not sure why)
>> and I can't get them to log onto the mapped network drives and the
>> exchange emails don't work. I can ping the Server IP and also access the
>> files via the IP address but not throught he Server name?
>>
>> First thing I would like to do is make sure that the script runs on all
>> the computers but I don't know where to find it? I am sure that it used
>> to run on all 6 PC's (XP Pro).
>>
>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's that
>> don't work I can't do that, it tells me that there domain isn't available
>> but if I 192.168.X.X then it brings the folder up OK.
>>
>> Any help greatly appreciated.
>><!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->

 

Lenny: The important part of Larry's post is the "/all" part of the
ipconfig.

Just because the ip address and netmask are the same doesn't necessarily
speak to the other parts that DHCP sets up when done properly. Subtle
things like default DNS suffix, etc, are all important and a cursory glance
won't tell you what you need to know. Based on your reply, I just felt it
important to reiterate that the /all flag is an important one in this
particular situation.

-Cliff


"lenny109" <lenny@thetakeout.com> wrote in message
news:LKednWHQLugr6iPXnZ2dnUVZ8sednZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Larry,
> Thanks for the reply. Yes you are correct in the first paragraph. You have
> managed to say in one paragraph exactly what I was trying to say in 4 long
> ones!
>
> I have checked all the IP's to make sure they are set to Auto and I also
> tried setting them to static then back to Auto as they are now. They can
> access the internet OK. IPconfig is the same (except for the IP address
> obviously) on both a working PC and one that isn't.
>
> I haven't flushed the DNS yet but will as soon as I can get back in the
> office.
>
> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
> message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> HI Lenny:
>>
>> Do I understand correctly that the remote office has 6 computers, half of
>> which can resolve the name of the SBS which is in a remote office, and
>> the other half cannot?
>>
>> Try this: start - run - cmd - type "ipconfig /all" without quotes, on
>> one that works and one that does not, and compare the results carefully.
>> The three that work are getting proper resolution from whatever DNS
>> server they are pointed to, the other three are not.
>>
>> Then, on the three that don't work, ipconfig /release, which should reset
>> the ip info to all 0's, followed by ipconfig /renew.
>>
>> Also, verify that both sets are setup to receive IP's from DHCP, and that
>> the three that don't work are not static left over from some prior
>> config.
>>
>> Then, after all the above: ipconfig /flushdns then ipconfig
>> /registerdns.
>>
>> And let us know the results.
>>
>> The logon script is in C:windowssysvol, iirc, but unless the
>> permissions are different, all users should run this on logon. I
>> sometimes put a pause in the script to verify it has actually run. If
>> you can't find it, on the SBS search for logon.bat. You should find two,
>> but they live in replicating folders so that changes to one copy will
>> appear in the other before you can open it.
>>
>> --
>> Larry
>> Please post the resolution to your
>> issue so that others may benefit.
>>
>> Get a Health Check for SBS at:
>>
>>
>>
>> "lenny109" <lenny@thetakeout.com> wrote in message
>> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi,
>>> I will try to explain my problem below but basically I would like to
>>> know why some computers can pick up the shared drives on the server and
>>> the others can't even though they all worked fine before the move?
>>>
>>> We have moved our offices to 2 new locations with the users in one
>>> office and the server to another office and setup a LAN to LAN VPN using
>>> Draytek routers. This is working fine. I have 6 pc's that log onto the
>>> network and then a script runs that sets up the mapped network drives.
>>> When this has run then the shared files, my docs, email (exchange
>>> server) and sage all work fine. My problem is that 3 of the PC's run
>>> this script at login and connect without any problems. 3 don't run the
>>> script (not sure why) and I can't get them to log onto the mapped
>>> network drives and the exchange emails don't work. I can ping the Server
>>> IP and also access the files via the IP address but not throught he
>>> Server name?
>>>
>>> First thing I would like to do is make sure that the script runs on all
>>> the computers but I don't know where to find it? I am sure that it used
>>> to run on all 6 PC's (XP Pro).
>>>
>>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's
>>> that don't work I can't do that, it tells me that there domain isn't
>>> available but if I 192.168.X.X then it brings the folder up OK.
>>>
>>> Any help greatly appreciated.
>>><!--colorc--><!--/colorc-->
>><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

Hi,
Yes, I understand.On this computer there is nothing in the Primary Dns
Suffix part.

As I will be under a bit of pressure to get it sorted on Monday is there
anything else that I can do if the Ipconfig /all shows no problems?
Also, if there is a descrepency between the IP details on the machines that
don't connect what should I do, or should the renew and flush/register do
the job?

Thanks
Lenny

"Cliff Galiher" <cgaliher@gmail.com> wrote in message
news:e3pFwVwPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Lenny: The important part of Larry's post is the "/all" part of the
> ipconfig.
>
> Just because the ip address and netmask are the same doesn't necessarily
> speak to the other parts that DHCP sets up when done properly. Subtle
> things like default DNS suffix, etc, are all important and a cursory
> glance won't tell you what you need to know. Based on your reply, I just
> felt it important to reiterate that the /all flag is an important one in
> this particular situation.
>
> -Cliff
>
>
> "lenny109" <lenny@thetakeout.com> wrote in message
> news:LKednWHQLugr6iPXnZ2dnUVZ8sednZ2d@pipex.net...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi Larry,
>> Thanks for the reply. Yes you are correct in the first paragraph. You
>> have managed to say in one paragraph exactly what I was trying to say in
>> 4 long ones!
>>
>> I have checked all the IP's to make sure they are set to Auto and I also
>> tried setting them to static then back to Auto as they are now. They can
>> access the internet OK. IPconfig is the same (except for the IP address
>> obviously) on both a working PC and one that isn't.
>>
>> I haven't flushed the DNS yet but will as soon as I can get back in the
>> office.
>>
>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>> message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> HI Lenny:
>>>
>>> Do I understand correctly that the remote office has 6 computers, half
>>> of which can resolve the name of the SBS which is in a remote office,
>>> and the other half cannot?
>>>
>>> Try this: start - run - cmd - type "ipconfig /all" without quotes, on
>>> one that works and one that does not, and compare the results carefully.
>>> The three that work are getting proper resolution from whatever DNS
>>> server they are pointed to, the other three are not.
>>>
>>> Then, on the three that don't work, ipconfig /release, which should
>>> reset the ip info to all 0's, followed by ipconfig /renew.
>>>
>>> Also, verify that both sets are setup to receive IP's from DHCP, and
>>> that the three that don't work are not static left over from some prior
>>> config.
>>>
>>> Then, after all the above: ipconfig /flushdns then ipconfig
>>> /registerdns.
>>>
>>> And let us know the results.
>>>
>>> The logon script is in C:windowssysvol, iirc, but unless the
>>> permissions are different, all users should run this on logon. I
>>> sometimes put a pause in the script to verify it has actually run. If
>>> you can't find it, on the SBS search for logon.bat. You should find
>>> two, but they live in replicating folders so that changes to one copy
>>> will appear in the other before you can open it.
>>>
>>> --
>>> Larry
>>> Please post the resolution to your
>>> issue so that others may benefit.
>>>
>>> Get a Health Check for SBS at:
>>>
>>>
>>>
>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...
>>>> Hi,
>>>> I will try to explain my problem below but basically I would like to
>>>> know why some computers can pick up the shared drives on the server and
>>>> the others can't even though they all worked fine before the move?
>>>>
>>>> We have moved our offices to 2 new locations with the users in one
>>>> office and the server to another office and setup a LAN to LAN VPN
>>>> using Draytek routers. This is working fine. I have 6 pc's that log
>>>> onto the network and then a script runs that sets up the mapped network
>>>> drives. When this has run then the shared files, my docs, email
>>>> (exchange server) and sage all work fine. My problem is that 3 of the
>>>> PC's run this script at login and connect without any problems. 3 don't
>>>> run the script (not sure why) and I can't get them to log onto the
>>>> mapped network drives and the exchange emails don't work. I can ping
>>>> the Server IP and also access the files via the IP address but not
>>>> throught he Server name?
>>>>
>>>> First thing I would like to do is make sure that the script runs on all
>>>> the computers but I don't know where to find it? I am sure that it used
>>>> to run on all 6 PC's (XP Pro).
>>>>
>>>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's
>>>> that don't work I can't do that, it tells me that there domain isn't
>>>> available but if I 192.168.X.X then it brings the folder up OK.
>>>>
>>>> Any help greatly appreciated.
>>>>
>>><!--colorc--><!--/colorc-->
>>
>> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

You can look in the advanced section of the TCP/IP settings. These *should*
get set by DHCP, but even that depends on if you are allowing SBS to be the
DHCP server as it should.

Until we know more, any "advice" would be a shotgun scatter. That just
isn't how I'm built to troubleshoot.

-Cliff


"lenny109" <lenny@thetakeout.com> wrote in message
news:gt6dnYyIhaRmpiLXnZ2dnUVZ8ladnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> Yes, I understand.On this computer there is nothing in the Primary Dns
> Suffix part.
>
> As I will be under a bit of pressure to get it sorted on Monday is there
> anything else that I can do if the Ipconfig /all shows no problems?
> Also, if there is a descrepency between the IP details on the machines
> that don't connect what should I do, or should the renew and
> flush/register do the job?
>
> Thanks
> Lenny
>
> "Cliff Galiher" <cgaliher@gmail.com> wrote in message
> news:e3pFwVwPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Lenny: The important part of Larry's post is the "/all" part of the
>> ipconfig.
>>
>> Just because the ip address and netmask are the same doesn't necessarily
>> speak to the other parts that DHCP sets up when done properly. Subtle
>> things like default DNS suffix, etc, are all important and a cursory
>> glance won't tell you what you need to know. Based on your reply, I just
>> felt it important to reiterate that the /all flag is an important one in
>> this particular situation.
>>
>> -Cliff
>>
>>
>> "lenny109" <lenny@thetakeout.com> wrote in message
>> news:LKednWHQLugr6iPXnZ2dnUVZ8sednZ2d@pipex.net...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi Larry,
>>> Thanks for the reply. Yes you are correct in the first paragraph. You
>>> have managed to say in one paragraph exactly what I was trying to say in
>>> 4 long ones!
>>>
>>> I have checked all the IP's to make sure they are set to Auto and I also
>>> tried setting them to static then back to Auto as they are now. They can
>>> access the internet OK. IPconfig is the same (except for the IP address
>>> obviously) on both a working PC and one that isn't.
>>>
>>> I haven't flushed the DNS yet but will as soon as I can get back in the
>>> office.
>>>
>>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>>> message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...
>>>> HI Lenny:
>>>>
>>>> Do I understand correctly that the remote office has 6 computers, half
>>>> of which can resolve the name of the SBS which is in a remote office,
>>>> and the other half cannot?
>>>>
>>>> Try this: start - run - cmd - type "ipconfig /all" without quotes, on
>>>> one that works and one that does not, and compare the results
>>>> carefully. The three that work are getting proper resolution from
>>>> whatever DNS server they are pointed to, the other three are not.
>>>>
>>>> Then, on the three that don't work, ipconfig /release, which should
>>>> reset the ip info to all 0's, followed by ipconfig /renew.
>>>>
>>>> Also, verify that both sets are setup to receive IP's from DHCP, and
>>>> that the three that don't work are not static left over from some prior
>>>> config.
>>>>
>>>> Then, after all the above: ipconfig /flushdns then ipconfig
>>>> /registerdns.
>>>>
>>>> And let us know the results.
>>>>
>>>> The logon script is in C:windowssysvol, iirc, but unless the
>>>> permissions are different, all users should run this on logon. I
>>>> sometimes put a pause in the script to verify it has actually run. If
>>>> you can't find it, on the SBS search for logon.bat. You should find
>>>> two, but they live in replicating folders so that changes to one copy
>>>> will appear in the other before you can open it.
>>>>
>>>> --
>>>> Larry
>>>> Please post the resolution to your
>>>> issue so that others may benefit.
>>>>
>>>> Get a Health Check for SBS at:
>>>>
>>>>
>>>>
>>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>>> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...
>>>>> Hi,
>>>>> I will try to explain my problem below but basically I would like to
>>>>> know why some computers can pick up the shared drives on the server
>>>>> and the others can't even though they all worked fine before the move?
>>>>>
>>>>> We have moved our offices to 2 new locations with the users in one
>>>>> office and the server to another office and setup a LAN to LAN VPN
>>>>> using Draytek routers. This is working fine. I have 6 pc's that log
>>>>> onto the network and then a script runs that sets up the mapped
>>>>> network drives. When this has run then the shared files, my docs,
>>>>> email (exchange server) and sage all work fine. My problem is that 3
>>>>> of the PC's run this script at login and connect without any problems.
>>>>> 3 don't run the script (not sure why) and I can't get them to log onto
>>>>> the mapped network drives and the exchange emails don't work. I can
>>>>> ping the Server IP and also access the files via the IP address but
>>>>> not throught he Server name?
>>>>>
>>>>> First thing I would like to do is make sure that the script runs on
>>>>> all the computers but I don't know where to find it? I am sure that it
>>>>> used to run on all 6 PC's (XP Pro).
>>>>>
>>>>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's
>>>>> that don't work I can't do that, it tells me that there domain isn't
>>>>> available but if I 192.168.X.X then it brings the folder up OK.
>>>>>
>>>>> Any help greatly appreciated.
>>>>>
>>>>
>>>
>>><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

"lenny109" <lenny@thetakeout.com> wrote in message
news:gt6dnYyIhaRmpiLXnZ2dnUVZ8ladnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> Yes, I understand.On this computer there is nothing in the Primary Dns
> Suffix part.
>
> As I will be under a bit of pressure to get it sorted on Monday is there
> anything else that I can do if the Ipconfig /all shows no problems?
> Also, if there is a descrepency between the IP details on the machines
> that don't connect what should I do, or should the renew and
> flush/register do the job?
>
> Thanks
> Lenny<!--colorc--><!--/colorc-->

Lenny,

If you can post an ipconfig /all from one that works, and one that doesn't,
we can evaluate it for you and make recommendations & suggestions. However,
as Cliff said, otherwise we'll be throwing out suggestions based on guess
work, which may cause confusion on your part. This will with at least being
specific for your scenario.

Also, does each site have a DC, or is the SBS at "headquarters" the only DC?
Does each site have a DHCP server? Is it the router?
Have all machines been joined to the SBS domain?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
for regional support phone numbers.

<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> "Cliff Galiher" <cgaliher@gmail.com> wrote in message
> news:e3pFwVwPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Lenny: The important part of Larry's post is the "/all" part of the
>> ipconfig.
>>
>> Just because the ip address and netmask are the same doesn't necessarily
>> speak to the other parts that DHCP sets up when done properly. Subtle
>> things like default DNS suffix, etc, are all important and a cursory
>> glance won't tell you what you need to know. Based on your reply, I just
>> felt it important to reiterate that the /all flag is an important one in
>> this particular situation.
>>
>> -Cliff
>>
>>
>> "lenny109" <lenny@thetakeout.com> wrote in message
>> news:LKednWHQLugr6iPXnZ2dnUVZ8sednZ2d@pipex.net...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi Larry,
>>> Thanks for the reply. Yes you are correct in the first paragraph. You
>>> have managed to say in one paragraph exactly what I was trying to say in
>>> 4 long ones!
>>>
>>> I have checked all the IP's to make sure they are set to Auto and I also
>>> tried setting them to static then back to Auto as they are now. They can
>>> access the internet OK. IPconfig is the same (except for the IP address
>>> obviously) on both a working PC and one that isn't.
>>>
>>> I haven't flushed the DNS yet but will as soon as I can get back in the
>>> office.
>>>
>>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>>> message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...
>>>> HI Lenny:
>>>>
>>>> Do I understand correctly that the remote office has 6 computers, half
>>>> of which can resolve the name of the SBS which is in a remote office,
>>>> and the other half cannot?
>>>>
>>>> Try this: start - run - cmd - type "ipconfig /all" without quotes, on
>>>> one that works and one that does not, and compare the results
>>>> carefully. The three that work are getting proper resolution from
>>>> whatever DNS server they are pointed to, the other three are not.
>>>>
>>>> Then, on the three that don't work, ipconfig /release, which should
>>>> reset the ip info to all 0's, followed by ipconfig /renew.
>>>>
>>>> Also, verify that both sets are setup to receive IP's from DHCP, and
>>>> that the three that don't work are not static left over from some prior
>>>> config.
>>>>
>>>> Then, after all the above: ipconfig /flushdns then ipconfig
>>>> /registerdns.
>>>>
>>>> And let us know the results.
>>>>
>>>> The logon script is in C:windowssysvol, iirc, but unless the
>>>> permissions are different, all users should run this on logon. I
>>>> sometimes put a pause in the script to verify it has actually run. If
>>>> you can't find it, on the SBS search for logon.bat. You should find
>>>> two, but they live in replicating folders so that changes to one copy
>>>> will appear in the other before you can open it.
>>>>
>>>> --
>>>> Larry
>>>> Please post the resolution to your
>>>> issue so that others may benefit.
>>>>
>>>> Get a Health Check for SBS at:
>>>>
>>>>
>>>>
>>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>>> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...
>>>>> Hi,
>>>>> I will try to explain my problem below but basically I would like to
>>>>> know why some computers can pick up the shared drives on the server
>>>>> and the others can't even though they all worked fine before the move?
>>>>>
>>>>> We have moved our offices to 2 new locations with the users in one
>>>>> office and the server to another office and setup a LAN to LAN VPN
>>>>> using Draytek routers. This is working fine. I have 6 pc's that log
>>>>> onto the network and then a script runs that sets up the mapped
>>>>> network drives. When this has run then the shared files, my docs,
>>>>> email (exchange server) and sage all work fine. My problem is that 3
>>>>> of the PC's run this script at login and connect without any problems.
>>>>> 3 don't run the script (not sure why) and I can't get them to log onto
>>>>> the mapped network drives and the exchange emails don't work. I can
>>>>> ping the Server IP and also access the files via the IP address but
>>>>> not throught he Server name?
>>>>>
>>>>> First thing I would like to do is make sure that the script runs on
>>>>> all the computers but I don't know where to find it? I am sure that it
>>>>> used to run on all 6 PC's (XP Pro).
>>>>>
>>>>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's
>>>>> that don't work I can't do that, it tells me that there domain isn't
>>>>> available but if I 192.168.X.X then it brings the folder up OK.
>>>>>
>>>>> Any help greatly appreciated.
>>>>>
>>>>
>>>
>>><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
>
><!--colorc--><!--/colorc-->

 

Hi,
All the computers were joined on the domain for the last few years as they
were all in the same office as the SBS. Now the SBS has been moved to
another office and that office is linked to this one with a Draytek Vigor
2820 router at both ends. These routers are providing a LAN to LAN network
(not just for the comptuers but also for the IP phones). Nothing has been
changed on the PC's. 3 connect as before, 3 don't. In both offices the DHCP
server is the Routers.

Any further advise will not confuse me but it will be appreciated.
Cheers.

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:OnVQCv4PKHA.5032@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "lenny109" <lenny@thetakeout.com> wrote in message
> news:gt6dnYyIhaRmpiLXnZ2dnUVZ8ladnZ2d@pipex.net...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi,
>> Yes, I understand.On this computer there is nothing in the Primary Dns
>> Suffix part.
>>
>> As I will be under a bit of pressure to get it sorted on Monday is there
>> anything else that I can do if the Ipconfig /all shows no problems?
>> Also, if there is a descrepency between the IP details on the machines
>> that don't connect what should I do, or should the renew and
>> flush/register do the job?
>>
>> Thanks
>> Lenny<!--colorc--><!--/colorc-->
>
> Lenny,
>
> If you can post an ipconfig /all from one that works, and one that
> doesn't, we can evaluate it for you and make recommendations &
> suggestions. However, as Cliff said, otherwise we'll be throwing out
> suggestions based on guess work, which may cause confusion on your part.
> This will with at least being specific for your scenario.
>
> Also, does each site have a DC, or is the SBS at "headquarters" the only
> DC?
> Does each site have a DHCP server? Is it the router?
> Have all machines been joined to the SBS domain?
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
> Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> for regional support phone numbers.
>
><!--coloro:green--><span style="color:green <!--/coloro-->
>>
>> "Cliff Galiher" <cgaliher@gmail.com> wrote in message
>> news:e3pFwVwPKHA.352@TK2MSFTNGP02.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Lenny: The important part of Larry's post is the "/all" part of the
>>> ipconfig.
>>>
>>> Just because the ip address and netmask are the same doesn't necessarily
>>> speak to the other parts that DHCP sets up when done properly. Subtle
>>> things like default DNS suffix, etc, are all important and a cursory
>>> glance won't tell you what you need to know. Based on your reply, I
>>> just felt it important to reiterate that the /all flag is an important
>>> one in this particular situation.
>>>
>>> -Cliff
>>>
>>>
>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>> news:LKednWHQLugr6iPXnZ2dnUVZ8sednZ2d@pipex.net...
>>>> Hi Larry,
>>>> Thanks for the reply. Yes you are correct in the first paragraph. You
>>>> have managed to say in one paragraph exactly what I was trying to say
>>>> in 4 long ones!
>>>>
>>>> I have checked all the IP's to make sure they are set to Auto and I
>>>> also tried setting them to static then back to Auto as they are now.
>>>> They can access the internet OK. IPconfig is the same (except for the
>>>> IP address obviously) on both a working PC and one that isn't.
>>>>
>>>> I haven't flushed the DNS yet but will as soon as I can get back in the
>>>> office.
>>>>
>>>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>>>> message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...
>>>>> HI Lenny:
>>>>>
>>>>> Do I understand correctly that the remote office has 6 computers, half
>>>>> of which can resolve the name of the SBS which is in a remote office,
>>>>> and the other half cannot?
>>>>>
>>>>> Try this: start - run - cmd - type "ipconfig /all" without quotes, on
>>>>> one that works and one that does not, and compare the results
>>>>> carefully. The three that work are getting proper resolution from
>>>>> whatever DNS server they are pointed to, the other three are not.
>>>>>
>>>>> Then, on the three that don't work, ipconfig /release, which should
>>>>> reset the ip info to all 0's, followed by ipconfig /renew.
>>>>>
>>>>> Also, verify that both sets are setup to receive IP's from DHCP, and
>>>>> that the three that don't work are not static left over from some
>>>>> prior config.
>>>>>
>>>>> Then, after all the above: ipconfig /flushdns then ipconfig
>>>>> /registerdns.
>>>>>
>>>>> And let us know the results.
>>>>>
>>>>> The logon script is in C:windowssysvol, iirc, but unless the
>>>>> permissions are different, all users should run this on logon. I
>>>>> sometimes put a pause in the script to verify it has actually run. If
>>>>> you can't find it, on the SBS search for logon.bat. You should find
>>>>> two, but they live in replicating folders so that changes to one copy
>>>>> will appear in the other before you can open it.
>>>>>
>>>>> --
>>>>> Larry
>>>>> Please post the resolution to your
>>>>> issue so that others may benefit.
>>>>>
>>>>> Get a Health Check for SBS at:
>>>>>
>>>>>
>>>>>
>>>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>>>> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...
>>>>>> Hi,
>>>>>> I will try to explain my problem below but basically I would like to
>>>>>> know why some computers can pick up the shared drives on the server
>>>>>> and the others can't even though they all worked fine before the
>>>>>> move?
>>>>>>
>>>>>> We have moved our offices to 2 new locations with the users in one
>>>>>> office and the server to another office and setup a LAN to LAN VPN
>>>>>> using Draytek routers. This is working fine. I have 6 pc's that log
>>>>>> onto the network and then a script runs that sets up the mapped
>>>>>> network drives. When this has run then the shared files, my docs,
>>>>>> email (exchange server) and sage all work fine. My problem is that 3
>>>>>> of the PC's run this script at login and connect without any
>>>>>> problems. 3 don't run the script (not sure why) and I can't get them
>>>>>> to log onto the mapped network drives and the exchange emails don't
>>>>>> work. I can ping the Server IP and also access the files via the IP
>>>>>> address but not throught he Server name?
>>>>>>
>>>>>> First thing I would like to do is make sure that the script runs on
>>>>>> all the computers but I don't know where to find it? I am sure that
>>>>>> it used to run on all 6 PC's (XP Pro).
>>>>>>
>>>>>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's
>>>>>> that don't work I can't do that, it tells me that there domain isn't
>>>>>> available but if I 192.168.X.X then it brings the folder up OK.
>>>>>>
>>>>>> Any help greatly appreciated.
>>>>>>
>>>>>
>>>>
>>>><!--colorc--><!--/colorc-->
>>
>><!--colorc--><!--/colorc-->
>
>
> <!--colorc--><!--/colorc-->

 

"lenny109" <lenny@thetakeout.com> wrote in message
news:EcednWiKGK0hDiLXnZ2dnUVZ8qOdnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> All the computers were joined on the domain for the last few years as they
> were all in the same office as the SBS. Now the SBS has been moved to
> another office and that office is linked to this one with a Draytek Vigor
> 2820 router at both ends. These routers are providing a LAN to LAN network
> (not just for the comptuers but also for the IP phones). Nothing has been
> changed on the PC's. 3 connect as before, 3 don't. In both offices the
> DHCP server is the Routers.
>
> Any further advise will not confuse me but it will be appreciated.
> Cheers.
><!--colorc--><!--/colorc-->


Hi Lenny,

Generally, it seems like a sound setup as long as there are no firewall
blocks, MTU changes from default in the routers, no NAT between sites (VPNs
are tunneled), not using ADSL, AD is not a single label name, if you ahven't
ran the wizard to configure the SBS when you moved it, if you've ran an
SBSBPA, using WINS, NetBIOS is not disabled, errors in the event logs, what
was changed during the switch over to the new office, routes have been
configured properly in the VPN configs, etc, etc... so you see, we'd be
throwing a whole list of things at you, which hopefully you can provide for
us as part of the troubleshooting process. Generalizations are difficult to
use with troublshooting without specifics. So the ipconfigs would help, for
starters. But I can understand if reluctant to post them.

Ace

 

Hi Ace,
I am not reluctant to post them. It is just that I am only back in the
office on Monday morning so can't post them until then but in the meantime I
was hoping to have a list of possibles to try. Mainly to save time because
as you are aware I am sure staff sat around doesn't go down to well.

I think the main indication of the problem must be that 3 of the PC's work
OK so that resolves many of the possibles you mentioned below I think. I am
fairly sure that the server is setup and running OK at the moment. Another
indication of this is that the 3 PC's that are connecting and working OK are
also using Exchange for emails and this is also sending and receiving OK,
the VPN also seems to be OK and as far as I am aware there isn't a limit to
the amount of traffic between the LANs. It is an ADSL connection at both
ends.

In fact, now that I have written this I am also thinking that this is
probably even in the wrong news group, I should have posted in an XP group
as my guess is the issue is with the PC and not the SBS. Although, if we
can't resolve the issue in this group then I don't think it will get
resolved any where else. Past experience. (We will resolve it I am
sure!)What do you think?

Cheers
Lenny

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:O2$Y835PKHA.4244@TK2MSFTNGP06.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "lenny109" <lenny@thetakeout.com> wrote in message
> news:EcednWiKGK0hDiLXnZ2dnUVZ8qOdnZ2d@pipex.net...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi,
>> All the computers were joined on the domain for the last few years as
>> they were all in the same office as the SBS. Now the SBS has been moved
>> to another office and that office is linked to this one with a Draytek
>> Vigor 2820 router at both ends. These routers are providing a LAN to LAN
>> network (not just for the comptuers but also for the IP phones). Nothing
>> has been changed on the PC's. 3 connect as before, 3 don't. In both
>> offices the DHCP server is the Routers.
>>
>> Any further advise will not confuse me but it will be appreciated.
>> Cheers.
>><!--colorc--><!--/colorc-->
>
>
> Hi Lenny,
>
> Generally, it seems like a sound setup as long as there are no firewall
> blocks, MTU changes from default in the routers, no NAT between sites
> (VPNs are tunneled), not using ADSL, AD is not a single label name, if you
> ahven't ran the wizard to configure the SBS when you moved it, if you've
> ran an SBSBPA, using WINS, NetBIOS is not disabled, errors in the event
> logs, what was changed during the switch over to the new office, routes
> have been configured properly in the VPN configs, etc, etc... so you see,
> we'd be throwing a whole list of things at you, which hopefully you can
> provide for us as part of the troubleshooting process. Generalizations are
> difficult to use with troublshooting without specifics. So the ipconfigs
> would help, for starters. But I can understand if reluctant to post them.
>
> Ace
> <!--colorc--><!--/colorc-->

 

My guess is that you have slightly different DHCP setups since each router
does its own.

1) Make SBS the DHCP server.
2) Configure the routers to forward DHCP traffic over the VPN. IF the
routers are designed for site-to-site VPN then the underlying network
*should* appear seamless to the clients, which in this case is obviously
*NOT* happening.
3) Without the ipconfigs, there is little more to be done at this point.

-Cliff


"lenny109" <lenny@thetakeout.com> wrote in message
news:EcednWiKGK0hDiLXnZ2dnUVZ8qOdnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> All the computers were joined on the domain for the last few years as they
> were all in the same office as the SBS. Now the SBS has been moved to
> another office and that office is linked to this one with a Draytek Vigor
> 2820 router at both ends. These routers are providing a LAN to LAN network
> (not just for the comptuers but also for the IP phones). Nothing has been
> changed on the PC's. 3 connect as before, 3 don't. In both offices the
> DHCP server is the Routers.
>
> Any further advise will not confuse me but it will be appreciated.
> Cheers.
>
> "Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
> news:OnVQCv4PKHA.5032@TK2MSFTNGP05.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> "lenny109" <lenny@thetakeout.com> wrote in message
>> news:gt6dnYyIhaRmpiLXnZ2dnUVZ8ladnZ2d@pipex.net...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi,
>>> Yes, I understand.On this computer there is nothing in the Primary Dns
>>> Suffix part.
>>>
>>> As I will be under a bit of pressure to get it sorted on Monday is there
>>> anything else that I can do if the Ipconfig /all shows no problems?
>>> Also, if there is a descrepency between the IP details on the machines
>>> that don't connect what should I do, or should the renew and
>>> flush/register do the job?
>>>
>>> Thanks
>>> Lenny<!--colorc--><!--/colorc-->
>>
>> Lenny,
>>
>> If you can post an ipconfig /all from one that works, and one that
>> doesn't, we can evaluate it for you and make recommendations &
>> suggestions. However, as Cliff said, otherwise we'll be throwing out
>> suggestions based on guess work, which may cause confusion on your part.
>> This will with at least being specific for your scenario.
>>
>> Also, does each site have a DC, or is the SBS at "headquarters" the only
>> DC?
>> Does each site have a DHCP server? Is it the router?
>> Have all machines been joined to the SBS domain?
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among responding engineers, and to help others benefit from your
>> resolution.
>>
>> Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
>> Messaging
>> Microsoft Certified Trainer
>>
>> For urgent issues, please contact Microsoft PSS directly. Please check
>> for regional support phone numbers.
>>
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>>
>>> "Cliff Galiher" <cgaliher@gmail.com> wrote in message
>>> news:e3pFwVwPKHA.352@TK2MSFTNGP02.phx.gbl...
>>>> Lenny: The important part of Larry's post is the "/all" part of the
>>>> ipconfig.
>>>>
>>>> Just because the ip address and netmask are the same doesn't
>>>> necessarily speak to the other parts that DHCP sets up when done
>>>> properly. Subtle things like default DNS suffix, etc, are all
>>>> important and a cursory glance won't tell you what you need to know.
>>>> Based on your reply, I just felt it important to reiterate that the
>>>> /all flag is an important one in this particular situation.
>>>>
>>>> -Cliff
>>>>
>>>>
>>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>>> news:LKednWHQLugr6iPXnZ2dnUVZ8sednZ2d@pipex.net...
>>>>> Hi Larry,
>>>>> Thanks for the reply. Yes you are correct in the first paragraph. You
>>>>> have managed to say in one paragraph exactly what I was trying to say
>>>>> in 4 long ones!
>>>>>
>>>>> I have checked all the IP's to make sure they are set to Auto and I
>>>>> also tried setting them to static then back to Auto as they are now.
>>>>> They can access the internet OK. IPconfig is the same (except for the
>>>>> IP address obviously) on both a working PC and one that isn't.
>>>>>
>>>>> I haven't flushed the DNS yet but will as soon as I can get back in
>>>>> the office.
>>>>>
>>>>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>>>>> message news:echFedtPKHA.352@TK2MSFTNGP02.phx.gbl...
>>>>>> HI Lenny:
>>>>>>
>>>>>> Do I understand correctly that the remote office has 6 computers,
>>>>>> half of which can resolve the name of the SBS which is in a remote
>>>>>> office, and the other half cannot?
>>>>>>
>>>>>> Try this: start - run - cmd - type "ipconfig /all" without quotes,
>>>>>> on one that works and one that does not, and compare the results
>>>>>> carefully. The three that work are getting proper resolution from
>>>>>> whatever DNS server they are pointed to, the other three are not.
>>>>>>
>>>>>> Then, on the three that don't work, ipconfig /release, which should
>>>>>> reset the ip info to all 0's, followed by ipconfig /renew.
>>>>>>
>>>>>> Also, verify that both sets are setup to receive IP's from DHCP, and
>>>>>> that the three that don't work are not static left over from some
>>>>>> prior config.
>>>>>>
>>>>>> Then, after all the above: ipconfig /flushdns then ipconfig
>>>>>> /registerdns.
>>>>>>
>>>>>> And let us know the results.
>>>>>>
>>>>>> The logon script is in C:windowssysvol, iirc, but unless the
>>>>>> permissions are different, all users should run this on logon. I
>>>>>> sometimes put a pause in the script to verify it has actually run.
>>>>>> If you can't find it, on the SBS search for logon.bat. You should
>>>>>> find two, but they live in replicating folders so that changes to one
>>>>>> copy will appear in the other before you can open it.
>>>>>>
>>>>>> --
>>>>>> Larry
>>>>>> Please post the resolution to your
>>>>>> issue so that others may benefit.
>>>>>>
>>>>>> Get a Health Check for SBS at:
>>>>>>
>>>>>>
>>>>>>
>>>>>> "lenny109" <lenny@thetakeout.com> wrote in message
>>>>>> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...
>>>>>>> Hi,
>>>>>>> I will try to explain my problem below but basically I would like to
>>>>>>> know why some computers can pick up the shared drives on the server
>>>>>>> and the others can't even though they all worked fine before the
>>>>>>> move?
>>>>>>>
>>>>>>> We have moved our offices to 2 new locations with the users in one
>>>>>>> office and the server to another office and setup a LAN to LAN VPN
>>>>>>> using Draytek routers. This is working fine. I have 6 pc's that log
>>>>>>> onto the network and then a script runs that sets up the mapped
>>>>>>> network drives. When this has run then the shared files, my docs,
>>>>>>> email (exchange server) and sage all work fine. My problem is that 3
>>>>>>> of the PC's run this script at login and connect without any
>>>>>>> problems. 3 don't run the script (not sure why) and I can't get them
>>>>>>> to log onto the mapped network drives and the exchange emails don't
>>>>>>> work. I can ping the Server IP and also access the files via the IP
>>>>>>> address but not throught he Server name?
>>>>>>>
>>>>>>> First thing I would like to do is make sure that the script runs on
>>>>>>> all the computers but I don't know where to find it? I am sure that
>>>>>>> it used to run on all 6 PC's (XP Pro).
>>>>>>>
>>>>>>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's
>>>>>>> that don't work I can't do that, it tells me that there domain isn't
>>>>>>> available but if I 192.168.X.X then it brings the folder up OK.
>>>>>>>
>>>>>>> Any help greatly appreciated.
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>><!--colorc--><!--/colorc-->
>>
>>
>><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

The worst thing you can do is go into an office and start "trying things."
It usually breaks more than it fixes, and then working back out of it is far
more problematic. Diagnose, diagnose, diagnose, and THEN act. Having a
list of things to do, all half baked, is a great way to leave your network
worse than you found it.

-Cliff


"lenny109" <lenny@thetakeout.com> wrote in message
news:Yp6dnd3KnOOlXyLXnZ2dnUVZ8jCdnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Ace,
> I am not reluctant to post them. It is just that I am only back in the
> office on Monday morning so can't post them until then but in the meantime
> I was hoping to have a list of possibles to try. Mainly to save time
> because as you are aware I am sure staff sat around doesn't go down to
> well.
>
> I think the main indication of the problem must be that 3 of the PC's work
> OK so that resolves many of the possibles you mentioned below I think. I
> am fairly sure that the server is setup and running OK at the moment.
> Another indication of this is that the 3 PC's that are connecting and
> working OK are also using Exchange for emails and this is also sending and
> receiving OK, the VPN also seems to be OK and as far as I am aware there
> isn't a limit to the amount of traffic between the LANs. It is an ADSL
> connection at both ends.
>
> In fact, now that I have written this I am also thinking that this is
> probably even in the wrong news group, I should have posted in an XP group
> as my guess is the issue is with the PC and not the SBS. Although, if we
> can't resolve the issue in this group then I don't think it will get
> resolved any where else. Past experience. (We will resolve it I am
> sure!)What do you think?
>
> Cheers
> Lenny
>
> "Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
> news:O2$Y835PKHA.4244@TK2MSFTNGP06.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> "lenny109" <lenny@thetakeout.com> wrote in message
>> news:EcednWiKGK0hDiLXnZ2dnUVZ8qOdnZ2d@pipex.net...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi,
>>> All the computers were joined on the domain for the last few years as
>>> they were all in the same office as the SBS. Now the SBS has been moved
>>> to another office and that office is linked to this one with a Draytek
>>> Vigor 2820 router at both ends. These routers are providing a LAN to LAN
>>> network (not just for the comptuers but also for the IP phones). Nothing
>>> has been changed on the PC's. 3 connect as before, 3 don't. In both
>>> offices the DHCP server is the Routers.
>>>
>>> Any further advise will not confuse me but it will be appreciated.
>>> Cheers.
>>><!--colorc--><!--/colorc-->
>>
>>
>> Hi Lenny,
>>
>> Generally, it seems like a sound setup as long as there are no firewall
>> blocks, MTU changes from default in the routers, no NAT between sites
>> (VPNs are tunneled), not using ADSL, AD is not a single label name, if
>> you ahven't ran the wizard to configure the SBS when you moved it, if
>> you've ran an SBSBPA, using WINS, NetBIOS is not disabled, errors in the
>> event logs, what was changed during the switch over to the new office,
>> routes have been configured properly in the VPN configs, etc, etc... so
>> you see, we'd be throwing a whole list of things at you, which hopefully
>> you can provide for us as part of the troubleshooting process.
>> Generalizations are difficult to use with troublshooting without
>> specifics. So the ipconfigs would help, for starters. But I can
>> understand if reluctant to post them.
>>
>> Ace
>><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

Hi Everybody,
Thanks for your help. I set the IP's of the computers that didn't work
statically to correspond with the ones that did work and now there is a
connection.
It is very very slow though so I will post another message about that.
Thanks again for all help and comments.

"lenny109" <lenny@thetakeout.com> wrote in message
news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> I will try to explain my problem below but basically I would like to know
> why some computers can pick up the shared drives on the server and the
> others can't even though they all worked fine before the move?
>
> We have moved our offices to 2 new locations with the users in one office
> and the server to another office and setup a LAN to LAN VPN using Draytek
> routers. This is working fine. I have 6 pc's that log onto the network
> and then a script runs that sets up the mapped network drives. When this
> has run then the shared files, my docs, email (exchange server) and sage
> all work fine. My problem is that 3 of the PC's run this script at login
> and connect without any problems. 3 don't run the script (not sure why)
> and I can't get them to log onto the mapped network drives and the
> exchange emails don't work. I can ping the Server IP and also access the
> files via the IP address but not throught he Server name?
>
> First thing I would like to do is make sure that the script runs on all
> the computers but I don't know where to find it? I am sure that it used to
> run on all 6 PC's (XP Pro).
>
> On the 3 PC's that work I can use 'run' \servername. On the 3 PC's that
> don't work I can't do that, it tells me that there domain isn't available
> but if I \192.168.X.X then it brings the folder up OK.
>
> Any help greatly appreciated.
> <!--colorc--><!--/colorc-->

 

"lenny109" <lenny@thetakeout.com> wrote in message
news:dbudnRWL_58BPF3XnZ2dnUVZ8oydnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Everybody,
> Thanks for your help. I set the IP's of the computers that didn't work
> statically to correspond with the ones that did work and now there is a
> connection.
> It is very very slow though so I will post another message about that.
> Thanks again for all help and comments.
><!--colorc--><!--/colorc-->

Not sure I folllow. You gave the machines that didn't work, the same IP of a
machine that does?

If so, are they on the same subnet?

Or are you talking about DNS IP entries?

Ace

 

Gateway, subnet mask and DNS Server address the same. Obviously their own
IP.

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:OFxH07DQKHA.4028@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> "lenny109" <lenny@thetakeout.com> wrote in message
> news:dbudnRWL_58BPF3XnZ2dnUVZ8oydnZ2d@pipex.net...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi Everybody,
>> Thanks for your help. I set the IP's of the computers that didn't work
>> statically to correspond with the ones that did work and now there is a
>> connection.
>> It is very very slow though so I will post another message about that.
>> Thanks again for all help and comments.
>><!--colorc--><!--/colorc-->
>
> Not sure I folllow. You gave the machines that didn't work, the same IP of
> a machine that does?
>
> If so, are they on the same subnet?
>
> Or are you talking about DNS IP entries?
>
> Ace
>
>
> <!--colorc--><!--/colorc-->

 

"lenny109" <lenny@thetakeout.com> wrote in message
news:KYqdnaBHJs7Bf13XnZ2dnUVZ8o2dnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Gateway, subnet mask and DNS Server address the same. Obviously their own
> IP.
><!--colorc--><!--/colorc-->

Ok. And their own gateway at their location, I think you meant, too.

So they were using some other DNS server?

Ace

 

Lenny,

No offense but setting the this stuff manually is just addressing a symptom
and not the root cause. You are ignoring the actual problem and moving
forward simply because what you did "worked." Sortof. So you've put up a
bad patchwork fix to address one issue, and then when we identify the
slowness issue you'll likely end up having to do some MORE dancework
(because of your previous custom changes) to make THAT work, and it ends up
being a virtual version of the Leaning Tower of Pisa....just waiting to
topple over and leave a whole pile of frustration in its wake. You'll reach
a point were all of these manual settings will become unmaintainable.

As previously suggested, you should post some ipconfig /all settings from
machines that work and machines that don't, as well as perhaps a bit of
information about your infrastructure so we understand how these PCs are
connected to SBS. We can help you fix this problem the *RIGHT* way.

-Cliff


"lenny109" <lenny@thetakeout.com> wrote in message
news:dbudnRWL_58BPF3XnZ2dnUVZ8oydnZ2d@pipex.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Everybody,
> Thanks for your help. I set the IP's of the computers that didn't work
> statically to correspond with the ones that did work and now there is a
> connection.
> It is very very slow though so I will post another message about that.
> Thanks again for all help and comments.
>
> "lenny109" <lenny@thetakeout.com> wrote in message
> news:u6idnVQtup823iPXnZ2dnUVZ8tCdnZ2d@pipex.net...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi,
>> I will try to explain my problem below but basically I would like to know
>> why some computers can pick up the shared drives on the server and the
>> others can't even though they all worked fine before the move?
>>
>> We have moved our offices to 2 new locations with the users in one office
>> and the server to another office and setup a LAN to LAN VPN using Draytek
>> routers. This is working fine. I have 6 pc's that log onto the network
>> and then a script runs that sets up the mapped network drives. When this
>> has run then the shared files, my docs, email (exchange server) and sage
>> all work fine. My problem is that 3 of the PC's run this script at login
>> and connect without any problems. 3 don't run the script (not sure why)
>> and I can't get them to log onto the mapped network drives and the
>> exchange emails don't work. I can ping the Server IP and also access the
>> files via the IP address but not throught he Server name?
>>
>> First thing I would like to do is make sure that the script runs on all
>> the computers but I don't know where to find it? I am sure that it used
>> to run on all 6 PC's (XP Pro).
>>
>> On the 3 PC's that work I can use 'run' servername. On the 3 PC's that
>> don't work I can't do that, it tells me that there domain isn't available
>> but if I 192.168.X.X then it brings the folder up OK.
>>
>> Any help greatly appreciated.
>><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->