Networking issue
14 September 2009, 11:59 AM
#1
Networking issue
Folks,
Maybe someone on here can help - networks are not my forte
We have a dedicated router for remote support for 2 specific sites of a big customer.
All works great.
We use a batch files to open and close gateways.
Here's the commands to open the gateway
Thats on an XP machine.
Windows 7 doesn't like the "Route Add" commands.
Its just says this operation requires elevation
Any ideas?
THanks,
Shaun
Maybe someone on here can help - networks are not my forte
We have a dedicated router for remote support for 2 specific sites of a big customer.
All works great.
We use a batch files to open and close gateways.
Here's the commands to open the gateway
Originally Posted by TheBatchFile
route add 0.0.0.0 mask 0.0.0.0 192.168.16.250
route add 10.31.103.0 mask 255.255.255.0 192.168.16.250
route add 10.31.103.0 mask 255.255.255.0 192.168.16.250
Windows 7 doesn't like the "Route Add" commands.
Its just says this operation requires elevation
Any ideas?
THanks,
Shaun
Last edited by urban; 14 September 2009 at 12:01 PM.
14 September 2009, 12:46 PM
#4
OK, I run as administrator and that fixes the initial problem, hoever I can't access remote site from windows 7
Here is a tracert on windows 7
C:\>tracert 10.31.10.28
Tracing route to kal [10.31.10.28]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.16.254
2 41 ms 41 ms 40 ms 88-212-191-128.rdns.as8401.net [88.212.191.128]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
Here is a tracert on XP
C:\>tracert 10.31.10.28
Tracing route to KAL [10.31.10.28]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.16.250
2 43 ms 42 ms 44 ms 82-198-152-155.nethop.ie [82.198.152.155]
3 44 ms 45 ms 46 ms 82-198-142-112.nethop.ie [82.198.142.112]
4 70 ms 71 ms 73 ms 82-198-152-159.nethop.ie [82.198.152.159]
5 71 ms 71 ms 72 ms KAL [10.31.10.28]
Trace complete.
Here is a tracert on windows 7
Originally Posted by Windows7Tracert
C:\>tracert 10.31.10.28
Tracing route to kal [10.31.10.28]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.16.254
2 41 ms 41 ms 40 ms 88-212-191-128.rdns.as8401.net [88.212.191.128]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
Here is a tracert on XP
Originally Posted by WindowsXPTracert
C:\>tracert 10.31.10.28
Tracing route to KAL [10.31.10.28]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.16.250
2 43 ms 42 ms 44 ms 82-198-152-155.nethop.ie [82.198.152.155]
3 44 ms 45 ms 46 ms 82-198-142-112.nethop.ie [82.198.142.112]
4 70 ms 71 ms 73 ms 82-198-152-159.nethop.ie [82.198.152.159]
5 71 ms 71 ms 72 ms KAL [10.31.10.28]
Trace complete.
14 September 2009, 01:32 PM
#5
The 2 traceroutes are going different routes:-
The batch file is for the wrong subnet:-
Looking at them, seems you need a route something along the lines of:-
route add 10.31.10.0 mask 255.255.255.0 192.168.16.250
Originally Posted by WindowsXPTracert
C:\>tracert 10.31.10.28
Tracing route to KAL [10.31.10.28]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.16.250
2 43 ms 42 ms 44 ms 82-198-152-155.nethop.ie [82.198.152.155]
3 44 ms 45 ms 46 ms 82-198-142-112.nethop.ie [82.198.142.112]
4 70 ms 71 ms 73 ms 82-198-152-159.nethop.ie [82.198.152.159]
5 71 ms 71 ms 72 ms KAL [10.31.10.28]
Trace complete.
Tracing route to KAL [10.31.10.28]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.16.250
2 43 ms 42 ms 44 ms 82-198-152-155.nethop.ie [82.198.152.155]
3 44 ms 45 ms 46 ms 82-198-142-112.nethop.ie [82.198.142.112]
4 70 ms 71 ms 73 ms 82-198-152-159.nethop.ie [82.198.152.159]
5 71 ms 71 ms 72 ms KAL [10.31.10.28]
Trace complete.
Originally Posted by Windows7Tracert
C:\>tracert 10.31.10.28
Tracing route to kal [10.31.10.28]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.16.254
2 41 ms 41 ms 40 ms 88-212-191-128.rdns.as8401.net [88.212.191.128]
Tracing route to kal [10.31.10.28]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.16.254
2 41 ms 41 ms 40 ms 88-212-191-128.rdns.as8401.net [88.212.191.128]
Originally Posted by TheBatchFile
route add 10.31.103.0 mask 255.255.255.0 192.168.16.250
route add 10.31.10.0 mask 255.255.255.0 192.168.16.250
14 September 2009, 01:38 PM
#6
Scooby Regular
Join Date: Oct 2005
Posts: 476
Likes: 0
Received 0 Likes
on
0 Posts
Do you realise that your original batch file was adding the route
route add 10.31.103.0 mask 255.255.255.0 192.168.16.250
and you were using tracert for
10.31.10.28
If I had to guess I'd say that you've created a route for 10.31.103.0 and so when you try to go to 10.31.10.28 it is just going to the default gateway.
If you do a tracert for 10.31.103.28 you'd probably find it went via the gateway 192.168.16.250
route add 10.31.103.0 mask 255.255.255.0 192.168.16.250
and you were using tracert for
10.31.10.28
If I had to guess I'd say that you've created a route for 10.31.103.0 and so when you try to go to 10.31.10.28 it is just going to the default gateway.
If you do a tracert for 10.31.103.28 you'd probably find it went via the gateway 192.168.16.250
Last edited by LostUser; 14 September 2009 at 01:40 PM.
14 September 2009, 02:00 PM
#7
OK, I know.
So how about we completely forget about line 2 of that batch file and just concentrate on line 1.
And your quite correct sir.
Originally it was only line 1 in the batch file "route add 0.0.0.0 mask 0.0.0.0 192.168.16.250"
Then they brought a second site into the equation and told us to add this to the batch file "route add 10.31.103.0 mask 255.255.255.0 192.168.16.250"
Worked OK with XP?
Just not with Vista or Win 7
So how about we completely forget about line 2 of that batch file and just concentrate on line 1.
If you do a tracert for 10.31.103.28 you'd probably find it went via the gateway 192.168.16.250
Originally it was only line 1 in the batch file "route add 0.0.0.0 mask 0.0.0.0 192.168.16.250"
Then they brought a second site into the equation and told us to add this to the batch file "route add 10.31.103.0 mask 255.255.255.0 192.168.16.250"
Worked OK with XP?
Just not with Vista or Win 7
Trending Topics
14 September 2009, 02:03 PM
#8
Update: just looked at a Unix server which has direct access to BOTH sites.
THis server in particular just has a static IP address on our network which is "192.168.16.99"
It does the following
"route add default 10.31.10.1"
THis server in particular just has a static IP address on our network which is "192.168.16.99"
It does the following
"route add default 10.31.10.1"
Last edited by urban; 14 September 2009 at 02:05 PM.
14 September 2009, 02:32 PM
#9
Scooby Regular
Join Date: Oct 2005
Posts: 476
Likes: 0
Received 0 Likes
on
0 Posts
By using
route add 0.0.0.0
you're effectively overwriting your default gateway. Are you assigning a default gateway to your clients via DHCP or other methods?
It may be that XP gave precedence to the route add 0.0.0.0 command but Vista gives precedence to the default gateway.
It would help if you could provide a "route print" and an "ipconfig" from a client that is having problems contacting the remote site.
route add 0.0.0.0
you're effectively overwriting your default gateway. Are you assigning a default gateway to your clients via DHCP or other methods?
It may be that XP gave precedence to the route add 0.0.0.0 command but Vista gives precedence to the default gateway.
It would help if you could provide a "route print" and an "ipconfig" from a client that is having problems contacting the remote site.
14 September 2009, 02:42 PM
#10
Originally Posted by LostUser
By using
route add 0.0.0.0
you're effectively overwriting your default gateway. Are you assigning a default gateway to your clients via DHCP or other methods?
route add 0.0.0.0
you're effectively overwriting your default gateway. Are you assigning a default gateway to your clients via DHCP or other methods?
I'm logged onto our internal network, I need to connect to the client
We used to change the gateway on the TCP/IP settings, then the client's gave us batch files to use instead - 1 to turn on and 1 to turn back off again
Originally Posted by LostUser
It would help if you could provide a "route print" and an "ipconfig" from a client that is having problems contacting the remote site.
14 September 2009, 03:25 PM
#12
OK - Windows 7 client
Originally Posted by IpConfigBefore
C:\>ipconfig
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::3568:88c8:d909:3264%12
IPv4 Address. . . . . . . . . . . : 192.168.16.32
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::216b:27e9:21e9:ae5b%11
IPv4 Address. . . . . . . . . . . : 192.168.16.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
Tunnel adapter isatap.SYSCODOM.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : SYSCODOM.local
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::3568:88c8:d909:3264%12
IPv4 Address. . . . . . . . . . . : 192.168.16.32
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::216b:27e9:21e9:ae5b%11
IPv4 Address. . . . . . . . . . . : 192.168.16.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
Tunnel adapter isatap.SYSCODOM.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : SYSCODOM.local
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Originally Posted by IpConfigAfter
C:\>ipconfig
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::3568:88c8:d909:3264%12
IPv4 Address. . . . . . . . . . . : 192.168.16.32
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::216b:27e9:21e9:ae5b%11
IPv4 Address. . . . . . . . . . . : 192.168.16.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
192.168.16.250
Tunnel adapter isatap.SYSCODOM.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : SYSCODOM.local
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::3568:88c8:d909:3264%12
IPv4 Address. . . . . . . . . . . : 192.168.16.32
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : SYSCODOM.local
Link-local IPv6 Address . . . . . : fe80::216b:27e9:21e9:ae5b%11
IPv4 Address. . . . . . . . . . . : 192.168.16.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.254
192.168.16.250
Tunnel adapter isatap.SYSCODOM.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : SYSCODOM.local
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Originally Posted by RoutePrintAfter
C:\>route print
================================================== =========================
Interface List
12...00 21 6a 53 35 04 ......Intel(R) WiFi Link 5300 AGN
11...00 23 ae 38 f0 82 ......Broadcom NetXtreme 57xx Gigabit Controller
1...........................Software Loopback Interface 1
13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
================================================== =========================
IPv4 Route Table
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.20 20
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.32 25
0.0.0.0 0.0.0.0 192.168.16.250 192.168.16.20 21
10.31.103.0 255.255.255.0 192.168.16.250 192.168.16.20 21
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.16.0 255.255.255.0 On-link 192.168.16.20 276
192.168.16.0 255.255.255.0 On-link 192.168.16.32 281
192.168.16.20 255.255.255.255 On-link 192.168.16.20 276
192.168.16.32 255.255.255.255 On-link 192.168.16.32 281
192.168.16.255 255.255.255.255 On-link 192.168.16.20 276
192.168.16.255 255.255.255.255 On-link 192.168.16.32 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.16.20 276
224.0.0.0 240.0.0.0 On-link 192.168.16.32 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.16.20 276
255.255.255.255 255.255.255.255 On-link 192.168.16.32 281
================================================== =========================
Persistent Routes:
None
IPv6 Route Table
================================================== =========================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
11 276 fe80::/64 On-link
12 281 fe80::/64 On-link
11 276 fe80::216b:27e9:21e9:ae5b/128
On-link
12 281 fe80::3568:88c8:d909:3264/128
On-link
1 306 ff00::/8 On-link
11 276 ff00::/8 On-link
12 281 ff00::/8 On-link
================================================== =========================
Persistent Routes:
None
================================================== =========================
Interface List
12...00 21 6a 53 35 04 ......Intel(R) WiFi Link 5300 AGN
11...00 23 ae 38 f0 82 ......Broadcom NetXtreme 57xx Gigabit Controller
1...........................Software Loopback Interface 1
13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
================================================== =========================
IPv4 Route Table
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.20 20
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.32 25
0.0.0.0 0.0.0.0 192.168.16.250 192.168.16.20 21
10.31.103.0 255.255.255.0 192.168.16.250 192.168.16.20 21
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.16.0 255.255.255.0 On-link 192.168.16.20 276
192.168.16.0 255.255.255.0 On-link 192.168.16.32 281
192.168.16.20 255.255.255.255 On-link 192.168.16.20 276
192.168.16.32 255.255.255.255 On-link 192.168.16.32 281
192.168.16.255 255.255.255.255 On-link 192.168.16.20 276
192.168.16.255 255.255.255.255 On-link 192.168.16.32 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.16.20 276
224.0.0.0 240.0.0.0 On-link 192.168.16.32 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.16.20 276
255.255.255.255 255.255.255.255 On-link 192.168.16.32 281
================================================== =========================
Persistent Routes:
None
IPv6 Route Table
================================================== =========================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
11 276 fe80::/64 On-link
12 281 fe80::/64 On-link
11 276 fe80::216b:27e9:21e9:ae5b/128
On-link
12 281 fe80::3568:88c8:d909:3264/128
On-link
1 306 ff00::/8 On-link
11 276 ff00::/8 On-link
12 281 ff00::/8 On-link
================================================== =========================
Persistent Routes:
None
14 September 2009, 03:35 PM
#13
Scooby Regular
Join Date: Oct 2005
Posts: 476
Likes: 0
Received 0 Likes
on
0 Posts
I'd say this is your problem
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.20 20
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.32 25
0.0.0.0 0.0.0.0 192.168.16.250 192.168.16.20 21
You effectively have 3 default routes. The highest priority being to 192.168.16.254
Rather than use the batch file to introduce a new default gateway you'd be better just specifiying the route for the network you're interested in.
Like this one which you can see in the route print
10.31.103.0 255.255.255.0 192.168.16.250 192.168.16.20 21
So just try
route add 10.31.10.0 mask 255.255.255.0 192.168.16.250
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.20 20
0.0.0.0 0.0.0.0 192.168.16.254 192.168.16.32 25
0.0.0.0 0.0.0.0 192.168.16.250 192.168.16.20 21
You effectively have 3 default routes. The highest priority being to 192.168.16.254
Rather than use the batch file to introduce a new default gateway you'd be better just specifiying the route for the network you're interested in.
Like this one which you can see in the route print
10.31.103.0 255.255.255.0 192.168.16.250 192.168.16.20 21
So just try
route add 10.31.10.0 mask 255.255.255.0 192.168.16.250
Thread
Thread Starter
Forum
Replies
Last Post
Phil3822
General Technical
0
30 September 2015 06:29 PM
