• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1323
  • Last Modified:

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)
0
lrmoore
Asked:
lrmoore
  • 5
  • 4
1 Solution
 
Matt VCommented:
Try telnetting to port 135 from the XP machine to the 2008 server:
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.
0
 
Coast-ITCommented:
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
0
 
Matt VCommented:
If it was a problem with the server service, the local PCs would not be able to access it either.
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
lrmooreAuthor Commented:
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.

0
 
lrmooreAuthor Commented:
Also, no Symantec or other AV /Firewall software installed on the 2008 server
0
 
Matt VCommented:
So it sounds like something is blocking WAN traffic at the 2008 server.  Maybe only the LAN addresses are alllowed to talk?
0
 
lrmooreAuthor Commented:
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
0
 
Matt VCommented:
Can the 2008 box ping the XP workstation on the other end?
0
 
lrmooreAuthor Commented:
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....
0
 
lrmooreAuthor Commented:
Finally got to the bottom of this.
Added a static route statement on the server in question:
 route add -p 10.0.2.0 mask 255.255.255.0 192.168.0.3  <== pointing to P2P router, not firewall

viola' - everything now works perfectly fine.
Go figure. For some reason, the NetGear firewall was redirecting ping packets just fine, but was having a hard time redirecting the netbios packets, and only from 2008 servers.

Oh well, all is happy now.

Thanks!
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now