Browsing Resources of Windows2008 server from XP across WAN
Have Win2008 server (not R2), 4-bit
No AD, no DNS
Using NetBios (NT4 domain) - don't ask, I didn't build this ...
WINS server on 2008 side/subnet
WINS server on XP side/subnet
WINS populates server name on both sides
2008 server can browse/access shares on 2003 WINS server on XP side
XP can see 2008 server in browse list.
Click on the server, and "network path not found" is the prevailing error message
Same issue from the 2003/WINS server on same subnet as the XP box
Can ping by name, IP address, ets
Can access all resources on 2008 server from all local PC's. By name, by IP address, by browse list, etc, no problems at all.
From remote site cannot even use \\ip address
But can ping by both IP address and Netbios name
Supposedly no firewalls between the two sites. Direct P2P T1 (I have no access to the local routers or I would certainly check this theory)
No AD, no DNS
Using NetBios (NT4 domain) - don't ask, I didn't build this ...
WINS server on 2008 side/subnet
WINS server on XP side/subnet
WINS populates server name on both sides
2008 server can browse/access shares on 2003 WINS server on XP side
XP can see 2008 server in browse list.
Click on the server, and "network path not found" is the prevailing error message
Same issue from the 2003/WINS server on same subnet as the XP box
Can ping by name, IP address, ets
Can access all resources on 2008 server from all local PC's. By name, by IP address, by browse list, etc, no problems at all.
From remote site cannot even use \\ip address
But can ping by both IP address and Netbios name
Supposedly no firewalls between the two sites. Direct P2P T1 (I have no access to the local routers or I would certainly check this theory)
Probably an issue with one of your services, most likely the server service.
Have a look in your event logs for any failing services. Have a look at your services by typing services.msc and see if the "server" service has been started.
If it doesn't start or wont start, its really easy to just unbind network sharing from the NIC, and rebind it again, thus creating a new instance of your server service.
If you are still having the same issue after this, go into the firewall (dont just stop the service), and disable it on all 3 profiles temporarily.
I have had the server service issue myself though, good luck
Have a look in your event logs for any failing services. Have a look at your services by typing services.msc and see if the "server" service has been started.
If it doesn't start or wont start, its really easy to just unbind network sharing from the NIC, and rebind it again, thus creating a new instance of your server service.
If you are still having the same issue after this, go into the firewall (dont just stop the service), and disable it on all 3 profiles temporarily.
I have had the server service issue myself though, good luck
If it was a problem with the server service, the local PCs would not be able to access it either.
ASKER
Good stuff. No connection using telnet to port 135
The people that "manage" the adtran routers swear that the SPI firewall is disabled and NetBios enabled. The won't give me the passwords so I can verify..
Firewall completely disabled, all profiles on 2008
I CAN access another server, Windows 2003 on same network as 2008 server from the same remote site. Actually there are 3 or 4 servers that are accessible with no problem from the remote site. It is only this one 2008 box...
It DID have 7, yes 7, NICs all connected to the network, all getting DHCP addresses.
I nixed that and only have 1 single NIC connected now until we get this sorted.
WINS, name resolution, all work fine.
The people that "manage" the adtran routers swear that the SPI firewall is disabled and NetBios enabled. The won't give me the passwords so I can verify..
Firewall completely disabled, all profiles on 2008
I CAN access another server, Windows 2003 on same network as 2008 server from the same remote site. Actually there are 3 or 4 servers that are accessible with no problem from the remote site. It is only this one 2008 box...
It DID have 7, yes 7, NICs all connected to the network, all getting DHCP addresses.
I nixed that and only have 1 single NIC connected now until we get this sorted.
WINS, name resolution, all work fine.
ASKER
Also, no Symantec or other AV /Firewall software installed on the 2008 server
So it sounds like something is blocking WAN traffic at the 2008 server. Maybe only the LAN addresses are alllowed to talk?
ASKER
Firewall completely off
Firewall on with explicit allow traffic from remote subnet and local subnet
Firewall on with explicit allow all traffic from all addresses on all interfaces
Same problem
Firewall on with explicit allow traffic from remote subnet and local subnet
Firewall on with explicit allow all traffic from all addresses on all interfaces
Same problem
Can the 2008 box ping the XP workstation on the other end?
ASKER
Oh yea, no problem.
Just found out that there is another remote site that is not having any issues.
I think I'm going to replace these Adtran routers on the P2P T1 with Cisco devices and see what happens.
The other remotes without issues connect via VPN...
What a mess....
Just found out that there is another remote site that is not having any issues.
I think I'm going to replace these Adtran routers on the P2P T1 with Cisco devices and see what happens.
The other remotes without issues connect via VPN...
What a mess....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
telnet ipof2008 135
See if it connects.. you should get a blank black screen where you can type.
If you get a connection timeout or error connecting, then traffic is blocked or not allowed for NETBIOS across the WAN.