WinGate Forums

by **rimas** » Nov 22 06 5:46 am

Hi!

I am still kinda new to WinGate, so I am hoping this is an easy problem to solve... I have a WinGate 6.0.4 server configured and from a client I am able to access both the Internet, and my corporate Intranet (via VPN software provided by my employer).

My problem is that I am unable to map a network drive (via the Windows 'net use' command) to the file server that was already running on the WinGate server machine (Win XP SP2).

But get this, if I reconfigure my client machine (also Win XP SP2, if it makes a difference) to no longer use the WinGate server machine as its DHCP server / DNS server / default gateway, I am once again able to connect to the file server on the WinGate server machine.

Again, since I am still kinda new to WinGate and not necessarily a networking expert (I know just enough to manage my little LAN here in my home office), I am hoping the solution is obvious to those more knowledgeable than myself.

Thanks,

Rimas

by **genie** » Nov 22 06 10:44 am

I wonder if your Wingate server routing is set in a way that prevents it to see your client machine?

by **rimas** » Nov 22 06 11:16 am

genie wrote:I wonder if your Wingate server routing is set in a way that prevents it to see your client machine?

I must admit I am not sure what you meant by your response, but let's see if I can answer your question anyway...

I defined a shared folder on my client machine. When the client is configured as a DHCP / DNS client of the WinGate machine, I am unable to get to \\<client machine>\<shared folder> from the WinGate server.

However, when the client is NOT configured to use the WinGate machine as its DHCP / DNS server, I AM able to get to \\<client machine>\<shared folder> from the WinGate server.

But I'm not sure what this shows as this is simply the opposite (or is it inverse?) of the same problem that I am trying to resolve...

What does Windows use when trying to establish a path to a shared folder on another machine (NetBIOS, WINS, ...?) and why would WinGate acting as a gateway prevent such access...?

Thanks,

Rimas

by **genie** » Nov 22 06 11:18 am

Can you email to me the routing tables from your wingate machine and your client? You can export routing tables to the text files by typing the following command in the command prompt window:

route print >routtable.txt

by **rimas** » Nov 22 06 11:40 am

genie wrote:Can you email to me the routing tables from your wingate machine and your client?

OK... here is the output from the client:

Code: Select all: =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 10 c6 cd 8d 2a ...... Intel(R) PRO/1000 MT Mobile Connection - Net Firewall Miniport Interfac e 0x3 ...00 00 00 00 00 01 ...... AGN Virtual Network Adapter - Net Firewall Miniport Interfac e 0x10005 ...00 05 4e 50 d4 32 ...... 11a/b/g Wireless LAN Mini PCI Adapter =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.101 192.168.1.188 10 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.1.0 255.255.255.0 192.168.1.188 192.168.1.188 10 192.168.1.188 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.1.255 255.255.255.255 192.168.1.188 192.168.1.188 10 224.0.0.0 240.0.0.0 192.168.1.188 192.168.1.188 10 255.255.255.255 255.255.255.255 192.168.1.188 3 1 255.255.255.255 255.255.255.255 192.168.1.188 192.168.1.188 1 255.255.255.255 255.255.255.255 192.168.1.188 10005 1 Default Gateway: 192.168.1.101 =========================================================================== Persistent Routes: None

...and here is the output from the (WinGate) server:

Code: Select all: =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x3 ...00 0f b5 45 53 9f ...... Realtek RTL8169/8110 Family Gigabit Ethernet NIC - Packet Scheduler Minipor t 0x10005 ...00 13 d4 90 c7 4c ...... Realtek RTL8139/810x Family Fast Ethernet NIC - Packet Scheduler Minipor t 0x40002 ...00 00 00 00 00 01 ...... AGN Virtual Network Adapter - Packet Scheduler Miniport =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 10 9.0.0.0 255.0.0.0 9.49.183.211 9.49.183.211 1 9.49.183.211 255.255.255.255 127.0.0.1 127.0.0.1 20 9.255.255.255 255.255.255.255 9.49.183.211 9.49.183.211 20 32.71.114.0 255.255.255.0 9.49.183.211 9.49.183.211 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 129.33.1.13 255.255.255.255 192.168.1.1 192.168.1.101 1 129.36.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 129.39.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 129.39.23.0 255.255.255.0 9.49.183.211 9.49.183.211 1 129.40.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 134.168.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 138.95.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 146.84.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 150.24.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 155.51.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 158.84.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 158.85.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 158.86.0.0 255.254.0.0 9.49.183.211 9.49.183.211 1 158.87.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 158.88.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 158.98.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 164.120.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 167.14.48.0 255.255.248.0 9.49.183.211 9.49.183.211 1 167.210.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 192.9.200.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.80.11.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.94.47.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.94.222.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.108.1.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.150.51.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.150.52.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.150.53.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.150.54.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 10 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 10 192.204.12.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.204.13.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.216.76.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.216.77.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.216.78.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.216.79.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.233.137.0 255.255.255.0 9.49.183.211 9.49.183.211 1 192.233.138.0 255.255.255.0 9.49.183.211 9.49.183.211 1 198.74.0.0 255.255.0.0 9.49.183.211 9.49.183.211 1 198.114.0.0 255.255.128.0 9.49.183.211 9.49.183.211 1 198.182.235.0 255.255.255.0 9.49.183.211 9.49.183.211 1 204.146.91.0 255.255.255.0 9.49.183.211 9.49.183.211 1 204.160.216.0 255.255.255.0 9.49.183.211 9.49.183.211 1 204.160.217.0 255.255.255.0 9.49.183.211 9.49.183.211 1 224.0.0.0 240.0.0.0 9.49.183.211 9.49.183.211 20 224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 10 255.255.255.255 255.255.255.255 9.49.183.211 10005 1 255.255.255.255 255.255.255.255 9.49.183.211 9.49.183.211 1 255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 1 Default Gateway: 192.168.1.1 =========================================================================== Persistent Routes: None

I hope this helps...

Cheers,

Rimas

by **genie** » Nov 22 06 11:58 am

Ok, it looks like there is some kind of a routing conflict - correct me if I am wrong - Wingate machine has its 192.168.0.0 route routed through its default gateway which goes through 192.168.1.1 - which potentially does not not how to route back to the 188 client. Can you try adding a route on your wingate machine like that:

route add 192.168.1.0 mask 255.255.255.0 192.168.1.101

?

by **rimas** » Nov 22 06 12:22 pm

genie wrote:route add 192.168.1.0 mask 255.255.255.0 192.168.1.101

OK, I entered the above command into a command prompt window, but I was still unable to access the shared folder on the server. Here are the only changes I noticed when I did another route print on the server and compared with the previous one...

Previously:

Code: Select all: 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 10 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 10

Now:

Code: Select all: 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 1 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.1.171 255.255.255.255 192.168.1.101 192.168.1.101 1

One line had its "metric" (whatever that is...) changed from 10 to 1. Also, a new entry appeared for 192.168.1.171. Note that this is not the address of the client I am testing with, but rather another client that is not currently configured to use WinGate as it's DHCP server / DNS server / gateway.

Any other ideas...?!?

Thanks,

Rimas

by **genie** » Nov 22 06 12:30 pm

Can you ping the server from the client?

by **Nev** » Nov 22 06 1:39 pm

rimas wrote:Hi!

I am still kinda new to WinGate, so I am hoping this is an easy problem to solve... I have a WinGate 6.0.4 server configured

Try upgrading to V6.1.4.

rimas wrote:My problem is that I am unable to map a network drive (via the Windows 'net use' command) to the file server that was already running on the WinGate server machine (Win XP SP2).

? Do you see any firewall hits when trying to connect.

========================================
You can install NETBEUI as a work around, although not supported it is available from the install CD under X:\VALUEADD\MSFT\NET\NETBEUI

With these instructions and precautions that it is not routable:

NetBEUI (NBF) is a non-routable protocol suitable for small networks.
Support for this protocol in Microsoft Windows has been discontinued.
If you are instructed by the Product Support Personnel to install this protocol
as a temporary measure, follow the instructions below.

Installation instructions for NetBEUI protocol on Windows XP and Windows 2002.

* copy nbf.sys into the %SYSTEMROOT%\SYSTEM32\DRIVERS\ directory
* copy netnbf.inf into the %SYSTEMROOT%\INF\ directory
* open network connection properties and use "Install..." button to add NetBEUI protocol
========================================

WinGate Forums

Unable to map network drive (i.e. net use) to WinGate server

Unable to map network drive (i.e. net use) to WinGate server

Re: Unable to map network drive (i.e. net use) to WinGate se

Who is online