Network Porblem on WAN

[Amit Tank]

facing a problem in Windows Server 2003 Standard Ed. with SP1.

Users from remote locations are not able to access shared resource on
file server over the WAN & giving error \\ServerName\ShareName is not
accessible The specified network name is no longer available.

While Same time users from remote location are able to access other
server and PC's.

LAN users are not facing any type of problem ot access share.

After restarting the Server It works fine, shared resource of file
server accessible from remote location.

[uwe schuh]

Hallo,

please check the wins-settings and the dns-settings.

I Think that these people who cannot connect have other settings then they
that can connect.


Bye

Uwe

Post by Amit Tank
facing a problem in Windows Server 2003 Standard Ed. with SP1.
Users from remote locations are not able to access shared resource on
file server over the WAN & giving error \\ServerName\ShareName is not
accessible The specified network name is no longer available.
While Same time users from remote location are able to access other
server and PC's.
LAN users are not facing any type of problem ot access share.
After restarting the Server It works fine, shared resource of file
server accessible from remote location.

[Ian]

Post by Amit Tank
facing a problem in Windows Server 2003 Standard Ed. with SP1.
Users from remote locations are not able to access shared resource on
file server over the WAN & giving error \\ServerName\ShareName is not
accessible The specified network name is no longer available.
While Same time users from remote location are able to access other
server and PC's.
LAN users are not facing any type of problem ot access share.
After restarting the Server It works fine, shared resource of file
server accessible from remote location.

Can you ping the hosts by IP address from remote locations?

[Amit Tank]

1. we can ping to ip
2. we can ping to server name
3. we can run nslookup and chek for name resolution will work shown ip
to name and name to ip perfectly
4. restart the server services and check but still not work.
5. \\ServerName\ShareName but not opening
6. \\ipaddress\sharename but not opening
7. replication is also works perfectly.
8. there is no more utilization of wan link ( around 40 % of 2 MBps )
9. we can log in through remote desktop. and works in the server from
remote site.

[Ian]

Post by Amit Tank
1. we can ping to ip
2. we can ping to server name
3. we can run nslookup and chek for name resolution will work shown ip
to name and name to ip perfectly
4. restart the server services and check but still not work.
5. \\ServerName\ShareName but not opening
6. \\ipaddress\sharename but not opening
7. replication is also works perfectly.
8. there is no more utilization of wan link ( around 40 % of 2 MBps )
9. we can log in through remote desktop. and works in the server from
remote site.

Can you ping the workstations in question from the server in question?

Ian

[Amit Tank]

There is problem in the perticuler one server other server and
workstation in same location works fine from any remote location.

[Ian]

Post by Amit Tank
There is problem in the perticuler one server other server and
workstation in same location works fine from any remote location.

Is the default gateway different on this server?

[Amit Tank]

same default gateway for the entire site.

But even without any changes after restart the server works perfectly
fine but after 3 - 4 days problem occurs again.

[Todd J Heron]

Install the latest NIC drivers.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Amit Tank" <***@gmail.com> wrote in message news:***@z14g2000cwz.googlegroups.com...
same default gateway for the entire site.

But even without any changes after restart the server works perfectly
fine but after 3 - 4 days problem occurs again.

[Amit Tank]

Latest NIC Driver was installed as per hardware vendor suggested.

Even set the speed of network card and switch from auto mode to 100
MBps manually. but still after 4-5 days problem occured.

[Todd J Heron]

Problem at the switch maybe? Plug the server into a different port on the
switch.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Amit Tank" <***@gmail.com> wrote in message news:***@z14g2000cwz.googlegroups.com...
Latest NIC Driver was installed as per hardware vendor suggested.

Even set the speed of network card and switch from auto mode to 100
MBps manually. but still after 4-5 days problem occured.

[Amit Tank]

I just found an article at Microsoft site there is some issue in Win2k3
SP1 with networking over the WAN specially when packets transfer from
router.

and mentoined that This problem occurs because the code incorrectly
increments the number of host routes on the computer when the code
modifies the MTU size of a host route.Because of the incorrect
increment, the number of host routes eventually reaches the maximum
value. After the maximum value is reached, the ICMP packets are
ignored.This inturn stops the commnunication over Wan.

http://support.microsoft.com/kb/898060/

Is it possible solution ?

[Todd J Heron]

I'd try a different port first.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Amit Tank" <***@gmail.com> wrote in message news:***@o13g2000cwo.googlegroups.com...
I just found an article at Microsoft site there is some issue in Win2k3
SP1 with networking over the WAN specially when packets transfer from
router.

and mentoined that This problem occurs because the code incorrectly
increments the number of host routes on the computer when the code
modifies the MTU size of a host route.Because of the incorrect
increment, the number of host routes eventually reaches the maximum
value. After the maximum value is reached, the ICMP packets are
ignored.This inturn stops the commnunication over Wan.

http://support.microsoft.com/kb/898060/

Is it possible solution ?

[Ian]

Post by Amit Tank
same default gateway for the entire site.
But even without any changes after restart the server works perfectly
fine but after 3 - 4 days problem occurs again.

So after 3 - 4 days the server drops out of the wan but operates
correctly on the lan?

[Amit Tank]

So after 3 - 4 days the server drops out of the wan but operates
correctly on the lan - YES user on lan can share / save the data on
this file server.

[Ian]

Post by Ian
So after 3 - 4 days the server drops out of the wan but operates
correctly on the lan - YES user on lan can share / save the data on
this file server.

Is the ip address static on the server?
is there Anything reported in event viewer?
any other devices (router etc. that could be issuing addresses in this
subnet)?
Are all required services still running when the server in unavailable
(Server, netlogon etc)?

Ian

[Amit Tank]

Is the ip address static on the server? yes static IP
is there Anything reported in event viewer? no such error regarding to
our problem
any other devices (router etc. that could be issuing addresses in this
subnet)? no noproblem.
Are all required services still running when the server in unavailable
(Server, netlogon etc)? yes works fine.

[Amit Tank]

I had just found on Microsoft site there are some issue in Win2k3 sp1
while using over the WAN .

http://support.microsoft.com/kb/898060/

and mentoined that

This problem occurs because the code incorrectly increments the number
of host routes on the computer when the code modifies the MTU size of a
host route. The maximum number of host routes is controlled by the
Registry Value in MaxIcmpHostRoutes. The default number of host routes
is 1,000. Because of the incorrect increment, the number of host routes
eventually reaches the maximum value. After the maximum value is
reached, the ICMP packets are ignored.

So is it the proper solution for this ?

[Ian]

Post by Amit Tank
I had just found on Microsoft site there are some issue in Win2k3 sp1
while using over the WAN .
http://support.microsoft.com/kb/898060/
and mentoined that
This problem occurs because the code incorrectly increments the number
of host routes on the computer when the code modifies the MTU size of a
host route. The maximum number of host routes is controlled by the
Registry Value in MaxIcmpHostRoutes. The default number of host routes
is 1,000. Because of the incorrect increment, the number of host routes
eventually reaches the maximum value. After the maximum value is
reached, the ICMP packets are ignored.
So is it the proper solution for this ?

What's your wins setup? Could it be that the wins record is being
removed (automatically)- This would explain why local users could access
it without any problem (as they will still find the server by broadcast)
wheras users not local to the server would be relying on Wins to find
the IP address of the server.

is the server in question a domain controller?

Do you replicate Wins between sites?

[Amit Tank]

WINS is not configured, name resolution done through only by AD
integrated DNS.

[Ian]

Post by Amit Tank
WINS is not configured, name resolution done through only by AD
integrated DNS.

I know you've been through the KB - Is anything in here relevant?

http://support.microsoft.com/?kbid=822219&SD=tech

Is the server a Domain Controller?

Ian

[Amit Tank]

Thanks Ian,

Even I had go throught this article it is relevent
we are facing below listed symptoms

You experience a temporary decrease in performance when you use a
program over the network. Performance typically slows down for
approximately 40 to 45 seconds. However, some delays may last up to 5
minutes.

A program that uses remote procedure call (RPC) or uses named pipes to
connect to a file server stops responding.

You receive an error message similar to one of the following messages
when you try to connect to a shared resource:
System error 64. The specified network name is no longer available.

You are intermittently disconnected from network resources, and you
cannot reconnect to the network resources on the file server. However,
you can ping the server, and you can use a Terminal Services session to
connect to the server.

So we are not using ARCserve Backup Agent, VERITAS Backup Exec,

We are using Veritas NetBackup 5.x but in this software Open
Transaction Manger funda is not used and there is not any file like
Otman4.sys or Otman5.sys

For resolution in this article

Restart the serve services

Use Performance Logs and Alerts to monitor theAvg. Disk Queue Length
but not much more

Disable opportunistic locking on the client. To disable opportunistic
locking on the client, set the following registry value to 1:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled

Use the Microsoft Configuration Capture Utility (MPS_REPORTS) I found
in DCDIAG some RPC and LDAP related BIND issuse while facing the
problem but after restart the server there is not any problem in DCDIAG
found.

Yes this is a ADC cum File server for same site.

[jasonm]

I am having the same problem
This is what i have found with help from Cisco

Our Windows 2003 Server has 2 nic cards in it..
one for the local network and one in the DMZ.

it seems that after applying server patch 1
Traffic on the inside card is being mis directed to the DMZ card.

This only happened after service patch 1.
We had to disable in the DMZ connection for all of the remote users over the
VPN to have access
this server again.

Does anyone have a better fix for this....

Post by Amit Tank
Thanks Ian,
Even I had go throught this article it is relevent
we are facing below listed symptoms
You experience a temporary decrease in performance when you use a
program over the network. Performance typically slows down for
approximately 40 to 45 seconds. However, some delays may last up to 5
minutes.
A program that uses remote procedure call (RPC) or uses named pipes to
connect to a file server stops responding.
You receive an error message similar to one of the following messages
System error 64. The specified network name is no longer available.
You are intermittently disconnected from network resources, and you
cannot reconnect to the network resources on the file server. However,
you can ping the server, and you can use a Terminal Services session to
connect to the server.
So we are not using ARCserve Backup Agent, VERITAS Backup Exec,
We are using Veritas NetBackup 5.x but in this software Open
Transaction Manger funda is not used and there is not any file like
Otman4.sys or Otman5.sys
For resolution in this article
Restart the serve services
Use Performance Logs and Alerts to monitor theAvg. Disk Queue Length
but not much more
Disable opportunistic locking on the client. To disable opportunistic
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled
Use the Microsoft Configuration Capture Utility (MPS_REPORTS) I found
in DCDIAG some RPC and LDAP related BIND issuse while facing the
problem but after restart the server there is not any problem in DCDIAG
found.
Yes this is a ADC cum File server for same site.

[Amit Tank]

Dear Jasonm

I found an article at Microsoft site there is some issue in Win2k3
SP1 with networking over the WAN specially when packets transfer from
router.

and mentoined that This problem occurs because the code incorrectly
increments the number of host routes on the computer when the code
modifies the MTU size of a host route.Because of the incorrect
increment, the number of host routes eventually reaches the maximum
value. After the maximum value is reached, the ICMP packets are
ignored.This inturn stops the commnunication over Wan.

http://support.microsoft.com/kb/898060/


Earlier we got this error within 4 days but After applying the patch
working fine since 10 days even speed of server is increase lots. . . .

[Ian]

Post by Amit Tank
Dear Jasonm
I found an article at Microsoft site there is some issue in Win2k3
SP1 with networking over the WAN specially when packets transfer from
router.
and mentoined that This problem occurs because the code incorrectly
increments the number of host routes on the computer when the code
modifies the MTU size of a host route.Because of the incorrect
increment, the number of host routes eventually reaches the maximum
value. After the maximum value is reached, the ICMP packets are
ignored.This inturn stops the commnunication over Wan.
http://support.microsoft.com/kb/898060/
Earlier we got this error within 4 days but After applying the patch
working fine since 10 days even speed of server is increase lots. . . .

I had this problem the other day on an RRAS box - The hotfix seems to
have sorted the problem

http://www.microsoft.com/downloads/details.aspx?FamilyID=a0245532-0ace-4b85-85bf-758e936173df&displaylang=en

Never thought of it being an issue here!!

Ian

[unknown]

Could be a faulty router antenna

--
bear
-----------------------------------------------------------------------
bear3's Profile: http://www.techhelpcentre.com/member.php?userid=2
View this thread: http://www.techhelpcentre.com/showthread.php?t=2102