Problem using Remote Server/Network

[JCFOWLER79]

Heres my set up at the office. Netopia router provided by covad. DHCP Off on the Netopia. 13 Public IP's. Netgear Firewall router, DHCP On, local address's 192.168.0.1 and up. Wingate VPN DHCP off. IP 192.168.0.45 static server. Dell laptop with wired and wireless network used to hook up. Heres my problem. When I plug into the Netopia and Statically assign an ip 66.134.184.198 subnet 255.255.255.240 I can log in through the NAT on the Netgear no problem can browse network use drives all is fine. When I connect through loacally (all behind the Netgear ie. my ip 192.168.0.100 Subnet 255.255.255.0) i get errors under Published routes. for the 192.168.0.0 I get ignored local conflict, and for 192.168.0.45 (server) i get in conflict. I do not see these messages when logged in through the Netopia with a public IP assigned to my machine. Then when I go home, behind another netgear with locals set up the same way as the office i get the same two errors. This results in me being unable to explore or map network drives. I never have any problem connecting at all I just think it has to do with these conflicts that I am having trouble. Any help would be great. If you need more info let me know.

Thanks
Jason

[JCFOWLER79]

I took a better look at some past posts.. Looks like I need to change my home network to a different local set up. I'll give 192.168.1.1 and see how that runs...am I on the right track. Also why is this the case? Just wondering if its TCP/IP practice or is it wingate vpn?

Jason

[jono659]

I ahd problems with x.x.0.x always i amusin 192.168.23.x

jono

[erwin]

Hi there Jason

You are on the right track.

Having the same IP addresses(or ranges) at either end of the VPN can mess with the routing of WinGate VPN.

Having one end use 192.168.0.* range (office) and the other end use 192.168.1.* (home) range should fix the routing conflicts that WinGate VPN is seeing. This way packets can easly be identified as to which end of the VPN they are supposed to be sent to.

Regards
Erwin

[JCFOWLER79]

OK I changed my dhcp pool at home and I no longer get the errors I was having before. Now the problem is in mapping and exploring the folders or shared drives on the server. I am able to connect and explore the computers on the network by name. All the drives, printers and folders show up as they should. I then try to explore the drive and nothing then after about a minute I get an error that the folder is not accessable. I try another shared folder and it works. Then I go back and try the folder that worked again it doesnt work. Same error as before. Now this was not happening from behind the Netopia at work just here at home. I did not change the subnet at home still 255.255.255.0. Should that be changed or is this error have to do with something else. I know the error is not on the server folders themselves (ie..folder share levels). Any help would be great. This seems like a great product if configured properly!

Thanks for the replys,

Jason

[jono659]

Think this may be an MTU problem try this

http://fishyfingerssl.com/phpBB2/viewto ... 1d12ba3974

[JCFOWLER79]

That was it, seems to work just fine now. I used 1350 for the MTU, should I go lower to get better speed or what? Thanks to all for the help.

Jason

[jono659]

Mine works just fine with 1350

JonO