E620 Datacard and LAN

[dracosveen]

Hi All,

It seems that what I thought was my 1st post was not actually....cos I can't find it.

So here goes again.

I have an E620 datacard and when I connect I loose my LAN/Wireless connection. I have tried numerous things and have searched the internet for a solution as according to some ppl I have spoken to I am supposed to be able to use both my datacard and LAN simultaneously.

So what I am trying to do is running my internet connection through the card and still be connected to my business network in order to be connected to the exchange server etc.

Initially I thought maybe it is some kind of routing problem cos I still have an ip addy on my LAN connection and it is still working, but my outlook looses connection to the server. I have tried adding the server to my hosts file but that did not work either.

Can some1 give me some advice or point me in the right direction.

Appreciate it
Draco

 

[ginggs]

Initially I thought maybe it is some kind of routing problem cos I still have an ip addy on my LAN connection and it is still working, but my outlook looses connection to the server.

I think you're on the right track. Without knowing how your office network is set up, I am guessing that your Exchange server is on a different subnet to your computer. When your E620 connects to the internet, its IP address becomes your default gateway, so any traffic for any subnet other than the one you're in gets routed through it.

What you need to do is find out the details of your office subnets and add persistent routes to the routing table on your PC so that it knows that to reach those subnets it needs to use your LAN connection's IP address.

 

[dracosveen]

Hey Ginggs,

Thanx for that. I had to go and read up on adding routes....cos I am just a normal programmer....but I digress.

Ok so my ip details are 172.25.17.37, 255.255.255.0, 172.25.17.1 and my exchange server is 172.10.32.19....so that is a totally different subnet or something right?

So I have to add a route to the exchange server (destination) with all its details.....which I need to get.....sigh....and our helpdesk is so fast.

Ok..will try that and let you know.

Thanx
Regards
Draco

 

[ginggs]

I had to go and read up on adding routes....cos I am just a normal programmer....

So what does that make me, an abnormal programmer?

Ok so my ip details are 172.25.17.37, 255.255.255.0, 172.25.17.1 and my exchange server is 172.10.32.19....so that is a totally different subnet or something right?

Your subnet mask is 255.255.255.0 so IP addresses in your subnet range from 172.25.17.1 to 172.25.17.254. Anything outside of this range needs to be sent via your router.

Please check that the IP address 172.10.32.19 is correct, that is a public address not a private address. Its IP address should be in the range 172.16.0.0 to 172.31.255.255.

 

[dracosveen]

Actually I think all programmers are abnormal

Public address? Well when I do a tracert and a ping on the exchange server name, that is the address that it resolves to. Is that problem?

I added the ping and tracert below so u can see....maybe I am doing something wrong.....and I am still waiting for the info from my helpdesk....but will it do any good with the address been public and all?

C:\Documents and Settings\10009115>ping srd-cle02

Pinging srd-cle02 [172.10.32.19] with 32 bytes of data:

Reply from 172.10.32.19: bytes=32 time<1ms TTL=127
Reply from 172.10.32.19: bytes=32 time<1ms TTL=127
Reply from 172.10.32.19: bytes=32 time<1ms TTL=127
Reply from 172.10.32.19: bytes=32 time<1ms TTL=127

Ping statistics for 172.10.32.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\10009115>tracert srd-cle02

Tracing route to srd-cle02 [172.10.32.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.25.17.1
2 <1 ms <1 ms <1 ms srd-cle02 [172.10.32.19]

Trace complete.

 

[ginggs]

Public address? Well when I do a tracert and a ping on the exchange server name, that is the address that it resolves to. Is that problem?

I think the person who set up your network cocked something up; they assumed all 172.x.y.z addresses were private. It is a problem in that from within your network you can never access any of the 'real' IP addresses in the range 172.0.0.0 to 172.15.255.255.

Try running the following command:

route /p ADD 172.10.0.0 MASK 255.255.0.0 172.25.17.1 METRIC 1

This should route traffic to any address in the range 172.10.0.1 to 172.10.255.254 via the router at 172.25.17.1.

 

[dracosveen]

Ginggs........U Biscut.

Who would have guessed that it was such a simple solution. I was also trying to add a route earlier thinking I could add like all the addresses.....but I obviously didn't know the correct ranges.

Anyway....working like a freaking charm.

Thanx again
Regards
Draco