similar to: Unusual TCP/IP Packet Size

Displaying 20 results from an estimated 200 matches similar to: "Unusual TCP/IP Packet Size"

2013 Oct 29
1
regression: msk0 watchdog timeout and interrupt storm
Hi Yonghyeon and All, >From time to time I use a notebook and boot FreeBSD from USB stick. FreeBSD 9.2-i386 works OK. So I tried to use FreeBSD 10.0-i386 BETA2 and the network adapter works for some 10-15 seconds and then stops with diagnostic message "msk0:watchdog timeout". I've found similar case at freebsd-current@ with no workaround. Yes, there is an interrupt storm as well.
2008 Feb 29
4
7.0 - slow/unstable Internet access via Linux router
Hello, recently I've installed 7.0 and now I'm observing strange thing with my Internet connection. Access to some sites may be VERY slow or doesn't work at all with different kinds of timeout messages or without messages at all (but other sites works fine). For example, firefox may say "Transferring data from..." message and then "The connection to the server was reset
2008 Sep 23
1
fxp multicast forwarding problems
Hi, Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. I was running PIM-SM and IGMPv2 router-mode on the box at the time. I wonder if this is related to the problems with fxp multicast transmission I saw back in April. I'm a bit concerned about this as fxp is still a very widespread and useful network chip. I am running
2012 Aug 02
5
IP range
Hi all Can someone explain me this: ifcfg-eth0-range1: ONBOOT="yes" IPADDR_START="192.168.1.48" IPADDR_END="192.168.1.55" CLONENUM_START="1" Why Bcast is 192.168.1.51 and why Mask is 255.255.255.252 ? OS: Centos 6.3/64bit Thanks Levi # ifconfig eth0:1 Link encap:Ethernet HWaddr 00:9C:02:99:FA:00 inet addr:192.168.1.48
2016 Nov 06
2
Logins differ for ip/DNS on ad dc
Thanks a lot for your help so far. The main reason I do not use vms is that the server is pretty limited in RAM so this would only be my last resort. To prevent confusion: srv.wie (192.168.1.50) is the same machine as smb.wie (192.168.1.55), I seperated them just now to debug the problem. > These look like they are being run on the DC, what about from the > windows clients ? > I did
2016 Nov 06
3
Logins differ for ip/DNS on ad dc
> > This sounds like a dns problem, are your windows machines using the DC > as their nameserver ? > yes they are using the server as dns. DNS is done through bind9 and implemented in samba via bind9_dlz. All looks fine: $ host -t A smb.wie smb.wie has address 192.168.1.50 $ host -t SRV _kerberos._udp.smb.wie _kerberos._udp.smb.wie has SRV record 0 100 88 srv.smb.wie. $ host -t SRV
2009 Dec 25
2
SIP Incoming / Inbound not working for Broadvoice (Asterisk PBX 1.6.1.6)
Hello, Please forgive me if I'm repeating this post. I have searched and looked for similar problem with a solution but have not see a similar one. My outgoing SIP and other channels work fine but the incoming/inbound SIP call goes straight to Broadvoice voicemail. I see that Broadvoice is registered when I look at the SIP registry. I have turned on SIP Debug and it is below. Anyone know
2015 Jul 13
2
Please help debug Windows setup
Hi, Thanks to John Wice for helping me with an earlier question. My two PCs behind the same router are still having problems connecting. Would appreciate thoughts on what I?m doing wrong? Router: Port 655 forwarded to 192.168.1.45, both TCP and UDP Port 656 forwarded to 192.168.1.51, both TCP and UDP Machine #1. ========== Local IP address on LAN = 192.168.1.45 Windows Firewall
1997 Sep 17
1
Smbclient fails to connect
Hi, I've recently upgrade to Samba 1.9.17p1 from 1.9.16p11 (for Solaris 2.5), but have now found that smbclient fails to connect to user shares on win95 machines. I've tried the same login account from a win95 account and am able to mount shares from other win 95 machines. I've also tried running the old smbclient binary with the new smbd & nmbd daemons, and that lets me log
2005 Sep 08
2
sip log messages every few seconds
This is a single aastra 9113i sip phone. asterisk 1.0.9 Why do I keep seeing this in the logs ? ------------------------------------------------------ Sep ?8 18:44:25 VERBOSE[18779]: Scheduling destruction of call '9157b7d5ef36e8ec556a68e446d4ad59@192.168.1.100' in 15000 ms Sep ?8 18:44:31 DEBUG[18779]: Setting NAT on RTP to 0 Sep ?8 18:44:31 VERBOSE[18779]: 11 headers, 2 lines Sep ?8
2004 Jul 20
2
SIP Registration issues
Hi, I've just (earlier today) updated from CVS so that I can apply the dtmf caller id patches. Unfortunately this has had an undesired effect. I have an intertex ix66 which up until the CVS update allowed me to register my * server with the ix66 for my local domain (eg sip.mydomain.com). Now it appears that asterisk gets totally confused and tries to register with itself! Anyone got any
2015 Jan 08
4
Asterisk 13.1.0/PJSIP peer IP address issue
Thank you for your note, Scott. I set rewrite_contact=yes for both contacts, and I also had to do remove_existing=yes because I had to remove the existing contact information (max_contacts = 1 was preventing new contact information) using pjsip qualify demo-alice etc., after which the right IP addresses showed in pjsip show endpoints. Anyway, it works as expected now, I think. My pjsip.conf is
2015 Jul 21
1
Please help debug Windows setup
Hi - Thanks to Sven-Haegar and Donald, but still having issues setting up with Windows. Machine1 can't ping the VPN address of machine2. Regular IPv4 address for both machines in 192.168.1.xxx range. Router: Forwarding port 655 to 101.102.103.1, UDP and TCP Forwarding port 656 to 101.102.103.2, UDP and TCP Tinc.conf on machine user1 just three lines: Name = vpnuser1 ConnectTo =
2004 Apr 20
2
WINS question
Morning everyone. Just have a quick question regarding WINS on samba-3.0.3. Running FreeBSD 4.9, with samba-3.0.3 built from the ports tree. The only thing I needed from this particular server at this time, was it to function as a WINS server for our company. I went ahead and did the basics, as setting the netbios name as well as saying 'yes' to wins support. However, I cannot tell if
2005 Jan 03
6
SipSak: error: this FQDN or IP is not valid: voicegw
Hi, I've tried to use SIPSAK to understand the troubles i'm having about sending my voice to the person I've called (extension), after doing this tests below I always got this error "error: this FQDN or IP is not valid: voicegw". This could cause problems (namely audio problems)? Best regards, Helder voicegw:~# sipsak -C empty -a password -s
2011 Oct 10
4
XCP 1.1.0 - how to use VNC for installing guest domains?
Hello, Is it required to install an additional VNC server on XCP 1.1.0 dom0 box (ip 192.168.1.50)to get access to VNC-windows for installing domU guests? As I don''t use m$ / XenCenter so I need VNC for installation of new guests. The VM is running (s. below) *but* I was not able to open VNC window to continue the installation (s. error message further below) # --- uuid ( RO)
2014 Apr 17
1
samba4 bind9_dlz and dhcp
Hai, ? A bit off topic in the samba forum, but i thinks this is the best place to ask. ? Im having?some troubles to get the dhcp server fully working with samba4. I dont think this is a samba problem, but as i did say here maybe the best placy to ask.. ? It works, but not totaly. The strange thing is for example. ? My debian client is now working.? It adds and deletes as it should.? No
2004 Jul 14
1
Slow Access
Before yesterday I had a perfectly (as far as I could tell) functioning PDC with samba, roaming profiles and all. Yesterday I made some changes to the server 1.) install dhcp3 server 2.) changed IPs from 192.168.1.50 to 192.168.1.1 3.) changed netbios name from garnet-base to garnetmain 4.) started two more interfaces eth1 (172.17.0.0/16) and eth2 (cable internet) eth0 is still 192.168.0.0/16
2008 Jul 31
1
PDC cannot become master browser; cannot change passwords
I am having two problems, possibly related, while performing pre-deployment testing of a Samba/OpenLDAP PDC with data that was vampired from an NT4 PDC. The Samba server fails to become a local master browser, and password change attempts (from a Windows client) fail. I followed Samba-Guide/ntmigration.html (taking some liberties with various items of configuration), ending with step #19.
2005 Oct 03
3
NET RPC calls fails
Hi Samba folks! I have a problem concerning RPC calls. In a domain environment running 3.0.3pre2 I have no problems shutting down remote computers. I now have a small environment with only 2 computers in a workgroup. My samba server is running on a FreeBSD 5.4 box and my client is a Win XP Pro SP2 box. When I try to use net rpc shutdown -I 192.168.1.50 -U Administrator i get the